[Webkit-unassigned] [Bug 14527] New: Presence of WebCore/ForwardingHeaders/JavaScriptCore breaks standalone WebCore build
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jul 4 22:52:35 PDT 2007
http://bugs.webkit.org/show_bug.cgi?id=14527
Summary: Presence of WebCore/ForwardingHeaders/JavaScriptCore
breaks standalone WebCore build
Product: WebKit
Version: 522+ (nightly)
Platform: Macintosh
OS/Version: Mac OS X 10.4
Status: NEW
Keywords: InRadar
Severity: Major
Priority: P1
Component: WebKit Misc.
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: bdash at webkit.org
WebCore needs to be able to build without having JavaScriptCore.framework in
the built products. In several places WebCore uses framework-style #includes
to pull in JavaScriptCore headers, such as InspectorController.h:33 which does
#include <JavaScriptCore/JSContextRef.h>
JSContextRef.h lives in the source under JavaScriptCore/API/JSContextRef.h. As
ForwardingHeaders is added to the header search path, any headers inside
ForwardingHeaders/JavaScriptCore will be found before those inside the system
JavaScriptCore.framework if there is no JavaScriptCore.framework in the built
products directory. ForwardingHeaders/JavaScriptCore exists at this point
because the Qt and Gdk ports do not have a "copy headers" build step which
copies headers into the structure that WebCore expects.
The end result: until this is resolved we need to manually remove
WebCore/ForwardingHeaders/JavaScriptCore before building WebCore standalone or
else the build will fail.
--
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list