RESOLVED FIXED 126329
JavaScriptCore/JSCallbackFunction.h is missing in tarball 
https://bugs.webkit.org/show_bug.cgi?id=126329
Summary JavaScriptCore/JSCallbackFunction.h is missing in tarball
Jeremy Huddleston Sequoia
Reported 2013-12-30 22:16:33 PST
The webkit-gtk tarball is missing JavaScriptCore/JSCallbackFunction.h which causes the build to fail. This is the case with 2.2.2 and 2.2.3 In file included from Source/JavaScriptCore/runtime/JSGlobalObject.cpp:83: ./Source/JavaScriptCore/API/ObjCCallbackFunction.h:32:9: fatal error: 'JavaScriptCore/JSCallbackFunction.h' file not found #import <JavaScriptCore/JSCallbackFunction.h> ^ To work around this, we're setting JSC_OBJC_API_ENABLED 0
Attachments
Add attachment proposed patch, testcase, etc.
Alberto Garcia
Comment 1 2014-01-03 10:58:12 PST
(In reply to comment #0) > The webkit-gtk tarball is missing > JavaScriptCore/JSCallbackFunction.h which causes the build to fail. > This is the case with 2.2.2 and 2.2.3 That file is actually in the tarball (as JavaScriptCore/API/JSCallbackFunction.h), but it looks like the forwarding header is not being generated in your case.
Jeremy Huddleston Sequoia
Comment 2 2014-01-03 11:17:53 PST
(In reply to comment #1) > (In reply to comment #0) > > The webkit-gtk tarball is missing > > JavaScriptCore/JSCallbackFunction.h which causes the build to fail. > > This is the case with 2.2.2 and 2.2.3 > > That file is actually in the tarball (as > JavaScriptCore/API/JSCallbackFunction.h), but it looks like the forwarding > header is not being generated in your case. Yes, Source/JavaScriptCore/API/JSCallbackFunction.h is present, but there is no JavaScriptCore/JSCallbackFunction.h. Where is it supposed to be generated from? I'll try to debug that.
Alberto Garcia
Comment 3 2014-01-03 15:58:19 PST
(In reply to comment #2) > there is no JavaScriptCore/JSCallbackFunction.h. > Where is it supposed to be generated from? I'll try to debug that. That should be generate-forwarding-headers.pl
Michael Catanzaro
Comment 4 2015-05-10 14:08:36 PDT
I believe this issue is obsolete based on comments in bug #126492. If this issue is still present in 2.8.1 or 2.9.1 please leave a note so we can reopen.
Note You need to log in before you can comment on or make changes to this bug.