That is right. They use the same output directory (so that existing scripts still work) but have different path schemes for data in that directory.
On Tue, Feb 7, 2012 at 1:44 PM, Adam Barth <[email protected]> wrote: > Nico, correct me if I'm wrong, but I believe you need to "rm -rf out" > if you're switching between the make build and the ninja build. > > Adam > > > On Tue, Feb 7, 2012 at 1:42 PM, Nico Weber <[email protected]> wrote: >> Hi, >> >> we recently made the webkit/chromium/mac port buildable with ninja, a >> new build system focused on build speed >> (http://martine.github.com/ninja/). I don't have any numbers for >> webkit standalone builds, but in a chromium checkout ninja is 20x as >> fast as make on empty builds (1s instead of 20s), and 120x as fast as >> xcodebuild. >> >> Giving it a try is easy: >> >> Tools/Scrips/update-webkit --chromium --ninja >> Tools/Scripts/build-webkit --chromium >> >> The output will appear in out/Release (or out/Debug if you do a debug build). >> >> Nico >> >> ps: If anybody is doing standalone webkit/chromium/linux builds: It's >> very easy to make that work with ninja, too. >> pps: Build perf numbers for make vs ninja for chromium builds: >> https://plus.google.com/101038813433650812235/posts/irc26fhRtPC >> _______________________________________________ >> webkit-dev mailing list >> [email protected] >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
