is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
Open the chrome/chrome.sln solution file in Visual Studio and build the solution. This can take from 10 minutes to 2 hours. More likely 1 hour.
If you just want the Chromium Browsers browser, and none of the tests, you can speed up your build by right-clicking the chromeproject in the solution explorer and selecting Build. You may want to make sure this project is the Startup project (which will display as bold) by right-clicking it and selecting Set as Startup Project. This will make Chromium download (as opposed to some random test) build and run when you press F5.
Accelerating the build
In decreasing order of speedup:
- Use a true multicore processor; ie. an Intel Core Duo or later; not a Pentium 4 HT.
- Use a x64 OS otherwise incremental linking is disabled.
- Have 8 gigs of RAM.
- Use VS2008 or do this manual fix for VS2005:
- Ensure that /MP is enabled. You can do this by creating a file called include.gypi which contains the following lines:
Put this file in a folder called .gyp under your home directory. On Windows, this will be something like: C:Documents and Settings.gypinclude.gypi, or if you are on Vista: C:Users.gypinclude.gypi. Use "mkdir %userprofile%.gyp" in a command prompt to create the folder because explorer may complain that you need to provide a file name. Make sure you run "gclient runhooks --force" after creating this file to rebuild the project files, forcing GYP to output /MP.
- Disable your anti-virus software for .ilk, .pdb, .cc, .h files and only check for viruses on modify. Disable scanning the directory where your sources reside.
- Store and build the Chromium code on a second hard drive. It won`t really speed up the build but at least your computer will stay responsive when you do gclient sync or a build.
- Defragment your hard drive regularly.
Rebuild / Clean
You can use Rebuild and Clean on individual projects to rebuild them. However, because of the large number of files generated by the build system, avoid using Rebuild All or Clean All - these do not erase everything! Instead delete the entire output directory (chromeDebug or chromeRelease).
Build Chromium with Command Line
You would need to have Visual Studio installed, but not running. Navigate to source directory (src/chrome) and type the following command:
C: runksrcchrome> devenv.exe /build Debug chrome.sln /project chrome.vcproj
You can also use devenv.com with the same command-line. This will show the output of the various build commands, which can be useful when trying to track down errors during building.
Note for Windows Vista: the devenv command may silently fail if Visual Studio has been configured to always run as Administrator. You can check or disable this by right clicking the Visual Studio application icon, then select Properties -> Compatibility -> Run this program as administrator.