Search results
You can Browse or Search the Chromium Code online. Chromium supports building on Windows, Mac and Linux host systems. Select the platform you want to build: Linux; Windows; Mac; Chrome OS (Build on Linux) linux-chromeos (runs the Chrome OS version of Chrome on Linux) cros-vm (runs in a Chrome OS virtual machine) "simplechrome" (runs on ...
- The Old Instructions for Getting The Code
To specify build parameters for GN builds, including release...
- Working With Branches
This applies to commits to Chromium repository branches. For...
- Gclient Managed Mode
For Developers > How-Tos > Get the Code: Checkout, Build, &...
- Working With Nested Third Party Repositories
The Chromium source tree includes other repositories in...
- Managing Multiple Working Directories
It only handles one single git repo though, and doesn't come...
- The Old Instructions for Getting The Code
Run Chromium. Once it is built, you can simply run the browser: $ out \Default\chrome. exe (The “.exe” suffix in the command is actually optional). Running test targets. Tests are split into multiple test targets based on their type and where they exist in the directory structure.
Get the code: check out, build, and run Chromium. Browse or Search Chromium Code online. Chromium supports building on Windows, Mac and Linux host systems. The process for building Chrome is generally the same on all platforms, but each platform has a few quirks.
Overview of RenderingNG. Read about the process of designing, building and shipping RenderingNG, a next-generation rendering architecture for Chromium. Read the doc. RenderingNG architecture. Understand components of the RenderingNG architecture, and how the rendering pipeline flows through them. Read the doc. Key data structures.
There is lots to learn about the Chromium code base, both at a macro level (how the processes are laid out, how IPC works, the flow of a URL load), and at a micro level (code idioms such as smart pointer usage guidelines, message loops, common threads, threading guidelines, string usage guidelines, etc).
Setting up the build. Chromium uses Ninja as its main build tool along with a tool called GN to generate .ninja files. You can create any number of build directories with different configurations. To create a build directory: $ gn gen out / Default. You only have to run this once for each new build directory, Ninja will update the build files ...
Getting started. You can use Visual Studio's built-in debugger or WinDBG to debug Chromium. You don't need to use the IDE to build in order to use the debugger: Ninja is used to build Chromium and most developers invoke it from a command prompt, and then open the IDE for debugging as necessary.
