Move JavaScriptCore to Sources
Created attachment 77434 [details] Patch
This patch doesn't actually contain the move because that would make the patch file huge. That means this will show up red on all the EWS bots. I'm going to hold off landing this patch until folks have plenty of warning. I just wanted to get it uploaded so folks could look at it and let me know what I screwed up.
Attachment 77434 [details] did not build on chromium: Build output: http://queues.webkit.org/results/7243188
Attachment 77434 [details] did not build on qt: Build output: http://queues.webkit.org/results/7200187
Attachment 77434 [details] did not build on gtk: Build output: http://queues.webkit.org/results/7209207
Attachment 77434 [details] did not build on win: Build output: http://queues.webkit.org/results/7286175
Comment on attachment 77434 [details] Patch rs=me.
http://trac.webkit.org/changeset/74855
One Qt buildfix landed in http://trac.webkit.org/changeset/74869 (Robert was faster than my svn update :) ) But we need one more fix for WebKit2, because WebKit2/Scripts/generate-forwarding-headers.pl can't handle the Sources/JavaScriptCore directory. I can check it 4-5 hours later. Or maybe Andras can be faster. :)
Thanks guys. Sorry for the hassle.
Qt-WK2 fix landed: http://trac.webkit.org/changeset/74873 (workaround) [Qt] run-javascriptcore-tests fix landed: http://trac.webkit.org/changeset/74874 [Qt] BuildSlaveSupport/built-product-archive fix landed: - http://trac.webkit.org/changeset/74875 - http://trac.webkit.org/changeset/74880 GTK fix landed: http://trac.webkit.org/changeset/74878 Trees are green again. :) Let's see the next rename bug! ;)