Summary: | Presence of WebCore/ForwardingHeaders/JavaScriptCore breaks standalone WebCore build | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Mark Rowe (bdash) <mrowe> | ||||
Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Major | CC: | alp, lars.knoll, staikos, zecke | ||||
Priority: | P1 | Keywords: | InRadar | ||||
Version: | 523.x (Safari 3) | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.4 | ||||||
Attachments: |
|
Description
Mark Rowe (bdash)
2007-07-04 22:52:34 PDT
The Qt and Gdk port build systems need to be changed to copy the headers into expected locations ASAP. We can't have this breaking the Mac build for long. I'm really not sure what we should do here. Copying the files is ugly and it seems like this is both an issue of using install-time headers during compile time, and of trying to hack around an OS X limitation by adding that limitation and workaround everywhere else too. I'm not overly concerned with how this is resolved. If you have a solution that will work without the copying of headers, please feel free to take that approach. Created attachment 15475 [details]
Move WebCore/ForwardingHeaders/JavaScriptCore away from WebCore
The most easy way is to copy the offending directory to a place not used by the MacPort. One proposal for such a directory would be JavaScriptCore/ForwardingHeaders.
Comment on attachment 15475 [details]
Move WebCore/ForwardingHeaders/JavaScriptCore away from WebCore
r=me
(In reply to comment #7) > Fixed by darin in r24210. Build fix by staikos in r24224. |