Bug 52150
Summary: | [Qt] ./WebKitTools/Scripts/build-webkit failed | ||
---|---|---|---|
Product: | WebKit | Reporter: | sandy paulanskaya <kuh3h3> |
Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WORKSFORME | ||
Severity: | Blocker | CC: | benjamin, paroga |
Priority: | P2 | Keywords: | Qt, QtTriaged |
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | Linux |
sandy paulanskaya
./WebKitTools/Scripts/build-webkit didn`t catch source directory change.
maybe recent svn source use Source/JavaScriptCore and Source/WebCore
but ./WebKitTools/Scripts/build-webkit still try to find old JavaScriptCore directory.
so compile failed.
[/media/sdc1/WebKit]$ LANG=C ./WebKitTools/Scripts/build-webkit --qt --release --qmake=qmake-qt4
Generating derived sources
Calling 'qmake-qt4 -r OUTPUT_DIR=/media/sdc1/WebKit/WebKitBuild/Release -r /media/sdc1/WebKit/DerivedSources.pro -o Makefile.DerivedSources' in /media/sdc1/WebKit/WebKitBuild/Release
Reading /media/sdc1/WebKit/Source/JavaScriptCore/DerivedSources.pro [/media/sdc1/WebKit/WebKitBuild/Release/Source/JavaScriptCore]
Reading /media/sdc1/WebKit/Source/WebCore/DerivedSources.pro [/media/sdc1/WebKit/WebKitBuild/Release/Source/WebCore]
Reading /media/sdc1/WebKit/WebKit/qt/Api/DerivedSources.pro [/media/sdc1/WebKit/WebKitBuild/Release/WebKit/qt/Api]
Calling 'make -f Makefile.DerivedSources generated_files' in /media/sdc1/WebKit/WebKitBuild/Release/JavaScriptCore
make: Entering directory `/media/sdc1/WebKit/WebKitBuild/Release/JavaScriptCore'
make: *** No rule to make target `../../../JavaScriptCore/DerivedSources.pro', needed by `Makefile.DerivedSources'. Stop.
make: Leaving directory `/media/sdc1/WebKit/WebKitBuild/Release/JavaScriptCore'
Failed to generate JavaScriptCore's derived sources!
of course There is no such file ../../../JavaScriptCore/DerivedSources.pro.
new source directory is ../../../Source/JavaScriptCore/DerivedSources.pro
please check it.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Patrick R. Gansterer
some directory structure changed over the last few weeks, but the problems should be fixed in the meantime.
is the problem still reproducible with current trunk?
Benjamin Poulain
Do a clean build. Something like that would have been catched by the bots :)