Changeset 48940 in webkit
- Timestamp:
- Sep 30, 2009 12:01:12 PM (15 years ago)
- Location:
- trunk/WebCore
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/WebCore/ChangeLog
r48939 r48940 1 2009-09-30 Chris Hawk <hawk@chromium.org> 2 3 Reviewed by Dimitri Glazkov. 4 5 Fix for conditionals in the WebCore gyp file, which contained two separate 6 'conditions' values for the webcore target. The first entry was ignored, 7 resulting in some missine defines. 8 https://bugs.webkit.org/show_bug.cgi?id=29907 9 10 * WebCore.gyp/WebCore.gyp: 11 1 12 2009-09-21 Jeremy Orlow <jorlow@chromium.org> 2 13 -
trunk/WebCore/WebCore.gyp/WebCore.gyp
r48937 r48940 160 160 'WEBCORE_NAVIGATOR_VENDOR="Google Inc."', 161 161 ], 162 'conditions': [163 ['OS=="linux"', {164 'defines': [165 # Mozilla on Linux effectively uses uname -sm, but when running166 # 32-bit x86 code on an x86_64 processor, it uses167 # "Linux i686 (x86_64)". Matching that would require making a168 # run-time determination.169 'WEBCORE_NAVIGATOR_PLATFORM="Linux i686"',170 ],171 }],172 ['OS=="mac"', {173 'defines': [174 # Match Safari and Mozilla on Mac x86.175 'WEBCORE_NAVIGATOR_PLATFORM="MacIntel"',176 177 # Chromium's version of WebCore includes the following Objective-C178 # classes. The system-provided WebCore framework may also provide179 # these classes. Because of the nature of Objective-C binding180 # (dynamically at runtime), it's possible for the Chromium-provided181 # versions to interfere with the system-provided versions. This may182 # happen when a system framework attempts to use WebCore.framework,183 # such as when converting an HTML-flavored string to an184 # NSAttributedString. The solution is to force Objective-C class185 # names that would conflict to use alternate names.186 187 # FIXME: This list will hopefully shrink but may also grow.188 # Periodically run:189 # nm libwebcore.a | grep -E '[atsATS] ([+-]\[|\.objc_class_name)'190 # and make sure that everything listed there has the alternate191 # ChromiumWebCoreObjC name, and that nothing extraneous is listed192 # here. If all Objective-C can be eliminated from Chromium's WebCore193 # library, these defines should be removed entirely.194 'ScrollbarPrefsObserver=ChromiumWebCoreObjCScrollbarPrefsObserver',195 'WebCoreRenderThemeNotificationObserver=ChromiumWebCoreObjCWebCoreRenderThemeNotificationObserver',196 'WebFontCache=ChromiumWebCoreObjCWebFontCache',197 ],198 }],199 ['OS=="win"', {200 'defines': [201 # Match Safari and Mozilla on Windows.202 'WEBCORE_NAVIGATOR_PLATFORM="Win32"',203 ],204 'dependencies': [205 # Needed on windows for some actions and rules206 '<(chromium_src_dir)/build/win/system.gyp:cygwin'207 ],208 }],209 ],210 162 'actions': [ 211 163 # Actions to build derived sources. … … 641 593 ], 642 594 }], 595 ['OS=="linux"', { 596 'defines': [ 597 # Mozilla on Linux effectively uses uname -sm, but when running 598 # 32-bit x86 code on an x86_64 processor, it uses 599 # "Linux i686 (x86_64)". Matching that would require making a 600 # run-time determination. 601 'WEBCORE_NAVIGATOR_PLATFORM="Linux i686"', 602 ], 603 }], 643 604 ['OS=="mac"', { 605 'defines': [ 606 # Match Safari and Mozilla on Mac x86. 607 'WEBCORE_NAVIGATOR_PLATFORM="MacIntel"', 608 609 # Chromium's version of WebCore includes the following Objective-C 610 # classes. The system-provided WebCore framework may also provide 611 # these classes. Because of the nature of Objective-C binding 612 # (dynamically at runtime), it's possible for the Chromium-provided 613 # versions to interfere with the system-provided versions. This may 614 # happen when a system framework attempts to use WebCore.framework, 615 # such as when converting an HTML-flavored string to an 616 # NSAttributedString. The solution is to force Objective-C class 617 # names that would conflict to use alternate names. 618 619 # FIXME: This list will hopefully shrink but may also grow. 620 # Periodically run: 621 # nm libwebcore.a | grep -E '[atsATS] ([+-]\[|\.objc_class_name)' 622 # and make sure that everything listed there has the alternate 623 # ChromiumWebCoreObjC name, and that nothing extraneous is listed 624 # here. If all Objective-C can be eliminated from Chromium's WebCore 625 # library, these defines should be removed entirely. 626 'ScrollbarPrefsObserver=ChromiumWebCoreObjCScrollbarPrefsObserver', 627 'WebCoreRenderThemeNotificationObserver=ChromiumWebCoreObjCWebCoreRenderThemeNotificationObserver', 628 'WebFontCache=ChromiumWebCoreObjCWebFontCache', 629 ], 644 630 'actions': [ 645 631 { … … 774 760 ], 775 761 'defines': [ 762 # Match Safari and Mozilla on Windows. 763 'WEBCORE_NAVIGATOR_PLATFORM="Win32"', 776 764 '__PRETTY_FUNCTION__=__FUNCTION__', 777 765 ],
Note: See TracChangeset
for help on using the changeset viewer.