On Sat, Jan 12, 2013 at 9:49 PM, Nico Weber <[email protected]> wrote: > On Tue, Dec 11, 2012 at 3:43 PM, Eric Seidel <[email protected]> wrote: >> Nevermind. After further discussion with Nico, this can't work yet. >> >> Ninja is currently configured to use a non-webkitty "out" build >> directory, which is undoubtably going to confus some scripts/bots. >> >> We'll try this again at a later time. Apologies for the noise. > > If you build WebKit/chromium on Linux (i.e. Chromium/Linux and > Chromium/Android), you're now using ninja. The Chromium Linux Release > and Chromium Android Release build bots seem to be working fine. > > Admire the exciting build output: > http://build.webkit.org/builders/Chromium%20Linux%20Release/builds/65467/steps/compile-webkit/logs/stdio > > Let us know if anything is not working for you. > > (If you must use make, you can pass --no-ninja to update-webkit, and > build-webkit will use make again. If you do this, please let me know > why.)
Chromium/Mac webkit builds now uses ninja by default too. The bot's build output is now a little more concise: http://build.webkit.org/builders/Chromium%20Mac%20Release/builds/53889/steps/compile-webkit/logs/stdio On my laptop, full builds are 10% faster and empty builds (the minimum time you need to wait for a build) are 30x as fast. If you still need xcodebuild, you can pass --no-ninja to update-webkit. Please let us know if and why you do this. Nico ps: Switching Chromium/Windows is blocked on http://crbug.com/169945, so it probably won't happen soon. _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
