RESOLVED FIXED 119103
ANGLE needs Windows build system
https://bugs.webkit.org/show_bug.cgi?id=119103
Summary ANGLE needs Windows build system
Alex Christensen
Reported 2013-07-25 13:32:09 PDT
The default ANGLE build system does not work well with WebKit. It builds to the wrong place, it does not work with some of our changes, it does not run bison as a build step, etc. There are enough changes to warrant replacing it with a separate build system, which we have already done for all other ports. I've made projects and property sheets that work, but I have prevented all configurations from building it because it isn't used yet and because I don't want to break anything.
Attachments
Patch (230.53 KB, patch)
2013-07-25 13:50 PDT, Alex Christensen
bfulgham: review+
bfulgham: commit-queue-
Alex Christensen
Comment 1 2013-07-25 13:50:25 PDT
Brent Fulgham
Comment 2 2013-07-25 14:01:59 PDT
Comment on attachment 207482 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=207482&action=review r=me > Source/ThirdParty/ANGLE/ANGLE.vcxproj/ANGLEGenerated.vcxproj:130 > + <NMakePreprocessorDefinitions>WIN32;NDEBUG;</NMakePreprocessorDefinitions> Stuff like this should be coming from the property sheets. Visual Studio seeds this automatically, so it's probably just a matter of deleting the "local" override of the settings from the property sheet. You can land as-is and we can clean up in a separate step.
Alex Christensen
Comment 3 2013-07-25 14:13:09 PDT
Alex Christensen
Comment 4 2013-07-25 14:15:26 PDT
(In reply to comment #2) > > Source/ThirdParty/ANGLE/ANGLE.vcxproj/ANGLEGenerated.vcxproj:130 > > + <NMakePreprocessorDefinitions>WIN32;NDEBUG;</NMakePreprocessorDefinitions> > > Stuff like this should be coming from the property sheets. Visual Studio seeds this automatically, so it's probably just a matter of deleting the "local" override of the settings from the property sheet. I'll clean this up in the upcoming patch where I make angle actually generate files in this project and use the bison output.
Note You need to log in before you can comment on or make changes to this bug.