Search results
Build Chromium (the "chrome" target) with Ninja using the command: $ autoninja -C out \D efault chrome autoninja is a wrapper that automatically provides optimal values for the arguments passed to ninja .
This can be done from the command line by passing these arguments to the Visual Studio installer that you download: --add Microsoft.VisualStudio.Workload.NativeDesktop. --add Microsoft.VisualStudio.Component.VC.ATLMFC --includeRecommended. You must have the Windows 10 SDK installed, version 10.0.15063 or later.
Right click on your "Chrome" shortcut. Choose properties. At the end of your "Target:" line add the command-line switch. For example: --disable-gpu-vsync. With that example flag, it should look like below (replacing "--disable-gpu-vsync" with any other command-line switch you want to use): chrome.exe --disable-gpu-vsync.
Built using Visual Studio 2022 v17.5.3 + SDK 10.0.22621.0 on Windows 10 virtual machine.
Build Chromium (the “chrome” target) with Ninja using the command: $ ninja - C out \Default chrome You can get a list of all of the other build targets from GN by running gn ls out/Default from the command line.
Store the build tree on a fast disk (preferably SSD). Still, expect build times of 30 minutes to 2 hours when everything has to be recompiled. Build Chromium. Build Chromium (the “chrome” target) with Ninja using the command: $ ninja -C out \Default chrome
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.
