In case you ever build Chromium for windows, and you don't closely follow chromium-dev:
---------- Forwarded message ---------- From: Scott Graham <[email protected]> Date: Tue, May 8, 2012 at 1:56 AM Subject: [chromium-dev] ninja build available on Windows To: chromium-dev <[email protected]> Hi, As of r135613, chromium can be built with ninja on Windows. This is helpful to get faster incremental builds compared with building in Visual Studio. Incremental linking is reliable when using the ninja build, and so can be on by default. This improves link time when iterating on a small set of .cc files by about 5x. You might prefer ninja's UI also. The ninja binary is in depot_tools, which means it's already in your path. http://code.google.com/p/chromium/wiki/NinjaBuild#Windows has details on how to use it. The summary is: set GYP_GENERATORS=ninja set GYP_DEFINES=component=shared_library incremental_chrome_dll=1 set GYP_MSVS_VERSION=2010 python build\gyp_chromium ninja -C out\Debug chrome.exe The ninja build isn't officially supported, but seems to work pretty well. If you run into any problems, please don't hack around them by modifying gyp files -- instead, ping Nico or me, and we'll fix them in gyp or ninja. scott PS: tools/vim/ninja-build.vim was updated to work on Windows (a "compile-this-file" command). Evan Martin and Nico Weber wrote the ninja gyp generator for the other platforms, Nico helped a lot with the Windows retargeting work, and Evan is the original author of ninja. -- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/a/chromium.org/group/chromium-dev -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
