Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(635)

Side by Side Diff: docs/linux_build_instructions.md

Issue 1318153003: [Docs] fixes (Closed) Base URL: https://chromium.googlesource.com/chromium/src@master
Patch Set: Created 5 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 # Build instructions for Linux 1 # Build instructions for Linux
2 2
3 [TOC] 3 [TOC]
4 4
5 ## Overview 5 ## Overview
6 6
7 Due its complexity, Chromium uses a set of custom tools to check out and build. 7 Due its complexity, Chromium uses a set of custom tools to check out and build.
8 Here's an overview of the steps you'll run: 8 Here's an overview of the steps you'll run:
9 9
10 1. **gclient**. A checkout involves pulling nearly 100 different SVN 10 1. **gclient**. A checkout involves pulling nearly 100 different SVN
11 repositories of code. This process is managed with a tool called `gclient`. 11 repositories of code. This process is managed with a tool called `gclient`.
12 1. **gyp**. The cross-platform build configuration system is called `gyp`, and 12 1. **gyp**. The cross-platform build configuration system is called `gyp`, and
13 on Linux it generates ninja build files. Running `gyp` is analogous to the 13 on Linux it generates ninja build files. Running `gyp` is analogous to the
14 `./configure` step seen in most other software. 14 `./configure` step seen in most other software.
15 1. **ninja**. The actual build itself uses `ninja`. A prebuilt binary is in 15 1. **ninja**. The actual build itself uses `ninja`. A prebuilt binary is in
16 `depot_tools` and should already be in your path if you followed the steps 16 `depot_tools` and should already be in your path if you followed the steps
17 to check out Chromium. 17 to check out Chromium.
18 1. We don't provide any sort of "install" step. 18 1. We don't provide any sort of "install" step.
19 1. You may want to [use a chroot](using_a_linux_chroot.md) to isolate yourself 19 1. You may want to [use a chroot](using_a_linux_chroot.md) to isolate yourself
20 from versioning or packaging conflicts (or to run the layout tests). 20 from versioning or packaging conflicts (or to run the layout tests).
21 21
22 ## Getting a checkout 22 ## Getting a checkout
23 23
24 * [Prerequisites](linux_build_instructions_prerequisites.md): what you need 24 * [Prerequisites](linux_build_instructions_prerequisites.md): what you need
25 before you build. 25 before you build.
26 * [Get the Code](http://dev.chromium.org/developers/how-tos/get-the-code): 26 * [Get the Code](http://dev.chromium.org/developers/how-tos/get-the-code):
27 check out the source code. 27 check out the source code.
28 28
29 **Note**. If you are working on Chromium OS and already have sources in 29 *** note
30 Note: if you are working on Chromium OS and already have sources in
30 `chromiumos/chromium`, you **must** run `chrome_set_ver --runhooks` to set the 31 `chromiumos/chromium`, you **must** run `chrome_set_ver --runhooks` to set the
31 correct dependencies. This step is otherwise performed by `gclient` as part of 32 correct dependencies. This step is otherwise performed by `gclient` as part of
32 your checkout. 33 your checkout.
34 ***
33 35
34 ## First Time Build Bootstrap 36 ## First Time Build Bootstrap
35 37
36 * Make sure your dependencies are up to date by running the 38 * Make sure your dependencies are up to date by running the
37 `install-build-deps.sh` script: 39 `install-build-deps.sh` script:
38 40
39 .../chromium/src$ build/install-build-deps.sh 41 .../chromium/src$ build/install-build-deps.sh
40 42
41 * Before you build, you should also 43 * Before you build, you should also
42 [install API keys](https://sites.google.com/a/chromium.org/dev/developers/ho w-tos/api-keys). 44 [install API keys](https://sites.google.com/a/chromium.org/dev/developers/ho w-tos/api-keys).
(...skipping 171 matching lines...) Expand 10 before | Expand all | Expand 10 after
214 * Want to use Eclipse as your IDE? See 216 * Want to use Eclipse as your IDE? See
215 [LinuxEclipseDev](linux_eclipse_dev.md). 217 [LinuxEclipseDev](linux_eclipse_dev.md).
216 * Built version as Default Browser? See 218 * Built version as Default Browser? See
217 [LinuxDevBuildAsDefaultBrowser](linux_dev_build_as_default_browser.md). 219 [LinuxDevBuildAsDefaultBrowser](linux_dev_build_as_default_browser.md).
218 220
219 ## Next Steps 221 ## Next Steps
220 222
221 If you want to contribute to the effort toward a Chromium-based browser for 223 If you want to contribute to the effort toward a Chromium-based browser for
222 Linux, please check out the [Linux Development page](linux_development.md) for 224 Linux, please check out the [Linux Development page](linux_development.md) for
223 more information. 225 more information.
OLDNEW
« no previous file with comments | « docs/how_to_extend_layout_test_framework.md ('k') | docs/linux_build_instructions_prerequisites.md » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698