RESOLVED FIXED 41725
REGRESSION(r62283): No longer possible to build for Tiger from SnowLeopard due to export file shenanigans
https://bugs.webkit.org/show_bug.cgi?id=41725
Summary REGRESSION(r62283): No longer possible to build for Tiger from SnowLeopard du...
Mark Rowe (bdash)
Reported 2010-07-06 17:18:54 PDT
In <http://trac.webkit.org/changeset/62283> an export file was added containing symbols that are only available when USE(ACCELERATED_COMPOSITING) is true. However, the manner in which it detects USE(ACCELERATED_COMPOSITING) being true only considers the build OS, not the OS that is being targeted. This results in WebCore failing to link when building for Tiger from SnowLeopard as the symbols from the accelerated compositing exports file are not present in any of the object files. This makes it impossible to build WebKit nightlies for Mac OS X.
Attachments
Patch (63.19 KB, patch)
2010-07-06 17:45 PDT, Mark Rowe (bdash)
no flags
Patch (64.51 KB, patch)
2010-07-06 17:50 PDT, Mark Rowe (bdash)
darin: review+
Mark Rowe (bdash)
Comment 1 2010-07-06 17:21:32 PDT
In order to address the more general issue here we need the selection of which symbols to export to follow the same logic that is used by the compiler when determining which features are enabled. One way to do this is to have the generation of the exports file handled via C++ code that uses the regular preprocessor macros to include or exclude symbols. I’m working on a patch that does just that.
Mark Rowe (bdash)
Comment 2 2010-07-06 17:45:26 PDT
Created attachment 60665 [details] Patch I'm not marking this for review quite yet as I'm still waiting on a build for Tiger from SnowLeopard to complete. I tested more normal build configurations successfully, and have eyeballed the output as well and everything looks correct.
Mark Rowe (bdash)
Comment 3 2010-07-06 17:50:05 PDT
Mark Rowe (bdash)
Comment 4 2010-07-06 18:02:03 PDT
Landed in r62608.
Eric Seidel (no email)
Comment 5 2010-07-06 18:02:06 PDT
Mark Rowe (bdash)
Comment 6 2010-07-06 18:13:53 PDT
A follow-up build fix was landed in r62609.
Note You need to log in before you can comment on or make changes to this bug.