[Webkit-unassigned] [Bug 75622] [chromium] after updating clang, incremental build doesn't work

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 5 10:54:15 PST 2012


--- Comment #3 from jochen at chromium.org  2012-01-05 10:54:15 PST ---
(In reply to comment #2)
> tools/clang/script/update.sh runs
>       find "out/${CONFIG}/obj.target" -name '*.gch' -exec rm {} +
> to clobber gch files after a clang update, but it has a hardcoded relative path from update.sh to the out dir that I suppose is wrong in a webkit standalone build. Bleh.
> Maybe the script could grow an optional build dir parameter?
> (To get unblocked, just run the command above on your out/ directory. I'll try to come up with a fix.)

ah, that may again collide with me using make instead of xcode?

I guess the script is executed in ./Source/WebKit/chromium, while the make build puts the stuff in ./out

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list