Summary: | REGRESSION(r177925): It broke the !ENABLE(INSPECTOR) build | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Csaba Osztrogonác <ossy> | ||||||
Component: | New Bugs | Assignee: | Csaba Osztrogonác <ossy> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Blocker | CC: | burg, commit-queue, japhet, kling, ossy | ||||||
Priority: | P1 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Bug Depends on: | |||||||||
Bug Blocks: | 139981 | ||||||||
Attachments: |
|
Description
Csaba Osztrogonác
2015-01-05 14:09:02 PST
Created attachment 244341 [details]
Patch
Comment on attachment 244341 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=244341&action=review > Source/WebCore/loader/appcache/ApplicationCacheGroup.cpp:582 > +#endif It is my understanding that all callsites into InspectorInstrumentation should not be guarded, since they are defined even if !ENABLE(INSPECTOR) and there are ENABLE(INSPECTOR) guards inside those methods. Is this file missing an #include or something to make it not compile? I would prefer to not have guards here. m_currentResourceIdentifier is inside ENABLE(INSPECTOR) guard which caused build failure in ApplicationCacheGroup.cpp. Unguarding fixes the build without changing the cpp. Created attachment 244344 [details]
Patch
Just a note, there were a discussion on IRC if !INSPECTOR build is useful or not. I checked the stripped binary size of the EFL WebKit library on x86_64. Disabling inspector decreases the original 43Mb with 1.2Mb, circa 2.8%. Comment on attachment 244344 [details]
Patch
Thanks!
Comment on attachment 244344 [details] Patch Clearing flags on attachment: 244344 Committed r178177: <http://trac.webkit.org/changeset/178177> All reviewed patches have been landed. Closing bug. |