OLD | NEW |
1 # Checking out and building Chromium on Linux | 1 # Checking out and building Chromium on Linux |
2 | 2 |
3 There are instructions for other platforms linked from the | 3 There are instructions for other platforms linked from the |
4 [get the code](get_the_code.md) page. | 4 [get the code](get_the_code.md) page. |
5 | 5 |
6 ## Instructions for Google Employees | 6 ## Instructions for Google Employees |
7 | 7 |
8 Are you a Google employee? See | 8 Are you a Google employee? See |
9 [go/building-chrome](https://goto.google.com/building-chrome) instead. | 9 [go/building-chrome](https://goto.google.com/building-chrome) instead. |
10 | 10 |
(...skipping 99 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
110 update the build files as needed. | 110 update the build files as needed. |
111 * You can replace `Default` with another name, but | 111 * You can replace `Default` with another name, but |
112 it should be a subdirectory of `out`. | 112 it should be a subdirectory of `out`. |
113 * For other build arguments, including release settings, see [GN build | 113 * For other build arguments, including release settings, see [GN build |
114 configuration](https://www.chromium.org/developers/gn-build-configuration). | 114 configuration](https://www.chromium.org/developers/gn-build-configuration). |
115 The default will be a debug component build matching the current host | 115 The default will be a debug component build matching the current host |
116 operating system and CPU. | 116 operating system and CPU. |
117 * For more info on GN, run `gn help` on the command line or read the | 117 * For more info on GN, run `gn help` on the command line or read the |
118 [quick start guide](../tools/gn/docs/quick_start.md). | 118 [quick start guide](../tools/gn/docs/quick_start.md). |
119 | 119 |
120 ### Faster builds | 120 ### <a id=faster-builds></a>Faster builds |
121 | 121 |
122 This section contains some things you can change to speed up your builds, | 122 This section contains some things you can change to speed up your builds, |
123 sorted so that the things that make the biggest difference are first. | 123 sorted so that the things that make the biggest difference are first. |
124 | 124 |
125 #### Disable NaCl | 125 #### Disable NaCl |
126 | 126 |
127 By default, the build includes support for | 127 By default, the build includes support for |
128 [Native Client (NaCl)](https://developer.chrome.com/native-client), but | 128 [Native Client (NaCl)](https://developer.chrome.com/native-client), but |
129 most of the time you won't need it. You can set the GN argument | 129 most of the time you won't need it. You can set the GN argument |
130 `enable_nacl=false` and it won't be built. | 130 `enable_nacl=false` and it won't be built. |
131 | 131 |
132 #### Include fewer debug symbols | 132 #### Include fewer debug symbols |
133 | 133 |
134 By default GN produces a build with all of the debug assertions enabled | 134 By default GN produces a build with all of the debug assertions enabled |
135 (`is_debug=true`) and including full debug info (`symbol_level=2`). Setting | 135 (`is_debug=true`) and including full debug info (`symbol_level=2`). Setting |
136 `symbol_level=1` will produce enough information for stack traces, but not | 136 `symbol_level=1` will produce enough information for stack traces, but not |
137 line-by-line debugging. Setting `symbol_level=0` will include no debug | 137 line-by-line debugging. Setting `symbol_level=0` will include no debug |
138 symbols at all. Either will speed up the build compared to full symbols. | 138 symbols at all. Either will speed up the build compared to full symbols. |
139 | 139 |
140 See [faster builds on Linux](linux_faster_builds.md) for various tips and | |
141 settings that may speed up your build. | |
142 | |
143 #### Disable debug symbols for Blink | 140 #### Disable debug symbols for Blink |
144 | 141 |
145 Due to its extensive use of templates, the Blink code produces about half | 142 Due to its extensive use of templates, the Blink code produces about half |
146 of our debug symbols. If you don't ever need to debug Blink, you can set | 143 of our debug symbols. If you don't ever need to debug Blink, you can set |
147 the GN arg `remove_webcore_debug_symbols=true`. | 144 the GN arg `remove_webcore_debug_symbols=true`. |
148 | 145 |
149 #### Use Icecc | 146 #### Use Icecc |
150 | 147 |
151 [Icecc](https://github.com/icecc/icecream) is the distributed compiler with a | 148 [Icecc](https://github.com/icecc/icecream) is the distributed compiler with a |
152 central scheduler to share build load. Currently, many external contributors use | 149 central scheduler to share build load. Currently, many external contributors use |
(...skipping 344 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
497 sudo ln -s /usr/share/fonts/truetype/verdanaz.ttf /usr/share/fonts/truetype/mstt
corefonts/Verdana_Bold_Italic.ttf | 494 sudo ln -s /usr/share/fonts/truetype/verdanaz.ttf /usr/share/fonts/truetype/mstt
corefonts/Verdana_Bold_Italic.ttf |
498 ``` | 495 ``` |
499 | 496 |
500 And then for the Java fonts: | 497 And then for the Java fonts: |
501 | 498 |
502 ```shell | 499 ```shell |
503 sudo mkdir -p /usr/share/fonts/truetype/ttf-lucida | 500 sudo mkdir -p /usr/share/fonts/truetype/ttf-lucida |
504 sudo find /usr/lib*/jvm/java-1.6.*-sun-*/jre/lib -iname '*.ttf' -print \ | 501 sudo find /usr/lib*/jvm/java-1.6.*-sun-*/jre/lib -iname '*.ttf' -print \ |
505 -exec ln -s {} /usr/share/fonts/truetype/ttf-lucida \; | 502 -exec ln -s {} /usr/share/fonts/truetype/ttf-lucida \; |
506 ``` | 503 ``` |
OLD | NEW |