[chromium] win10 vs2019 environment chromium configuration and compilation.

Hardware & software configuration

System requirements ：

vs2019 demand ： The best default path , Reduce the trouble .

• desktop c++
  • mfc、atl
• .>= 10.0.19041 win10 SDK
  • SDK Debugging Tools, Check install in the control panel program

    • Control Panel → Programs → Programs and Features → Select the “Windows Software Development Kit” → Change → Change → Check “Debugging Tools For Windows” → Change.

install depot_tools

Download link

• download
• environment variable path add to depot_tools The installation path
• System variables add DEPOT_TOOLS_WIN_TOOLCHAIN , And set to 0
• Press the following command in cmd Set up your own VS route
  • set vs2019_install=C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional
  • gclient
    • For installation windows Things needed , Such as mysysgit 、python
• determine python install
  • where python determine python.bat stay python.exe. Before

get the code

You usually need to set up a proxy / There are global agents

$ git config --global user.name "My Name" 
$ git config --global user.email "[email protected]"
$ git config --global core.autocrlf false
$ git config --global core.filemode false
$ git config --global branch.autosetuprebase always

• fetch Code
  • fetch --no-history chromium Do not download historical information
    • Probability requires agency , interrupts , Use gclient sync Sync
    • If you need historical information , Debug fixed version with fallback , It's better to keep history .

• There was a mistake ： It should be an agency problem ？ Not downloaded to this file .
  • Failed to download prebuilt clang package clang-llvmorg-14-init-17086-g38e16e1c-6.tgz Use build.py if you want to build locally. Exiting.
• And then use gclient sync Sync .
  • Problems arise ： To the corresponding error Just delete all folders and resynchronize them .
    • Syncing projects: 85% (18/21) src/third_party/angle src/docs/website (ERROR)

compile

• gn gen --ide=vs out\build Generate vs engineering （ have access to VS Compile the , Or use the command line ninja compile ）

  • Get the results ：
    • Generating Visual Studio projects took 12001ms Done. Made 17069 targets from 2996 files in 43099ms

• ninja -C out\build chrome Use ninja compile （ It will take a long time ）（ Errors can be repeated incrementally ？）

  • result ：[52062/52062] STAMP obj/chrome/chrome.stamp

• Sure VS open .exe Step by step debugging .

• Sure VS open all.sln GN Compile debugging .

  • 

Compilation acceleration

• By using sccache Use cache to speed up chromium compile ;
  - sccache have access to scoop Tools scoop install sccache download .
  - scoop Tool pass powershell download ：Invoke-Expression (New-Object System.Net.WebClient).DownloadString('https://get.scoop.sh')
  - Will usually sccache Capacity expansion to 30Gset SCCACHE_CACHE_SIZE="30G"

Basic concepts

• gn & ninja

  • gn amount to cmake;ninja amount to make;
    • gn replace GYP,GYP replace CMake .gn use C++ Write , Increase speed .
      • GYP Compare with CMake：GYP Configuration file writing method Emphasis on modularity 、 structured .
    • gn Use Ninja replace Make As a new build tool .Ninja Pursue speed , Reduce features to speed up compilation ,
      • ninja Use build.ninja Define build rules , amount to make Of Makefile.
  • Chromium Use Ninja As a compiler , Use GN Generate .ninja The configuration file

• so many projects

  • Solution file .sln There are too many projects in , Find what you want to see .
  • then attach On the process debug