docs/common_build_tasks.md - Issue 2545363002: Use HTTPS links for Google domains in docs

Side by Side Diff: docs/common_build_tasks.md

Issue 2545363002: Use HTTPS links for Google domains in docs (Closed)

Patch Set: Modify two more files in subdirectories Created 4 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

« no previous file with comments | « docs/closure_compilation.md ('k') | docs/git_cookbook.md » ('j') | no next file with comments »

OLD	NEW
1 # Common Build Tasks	1 # Common Build Tasks

2	2

3 The Chromium build system is a complicated beast of a system, and it is not very	3 The Chromium build system is a complicated beast of a system, and it is not very

4 well documented beyond the basics of getting the source and building the	4 well documented beyond the basics of getting the source and building the

5 Chromium product. This page has more advanced information about the build	5 Chromium product. This page has more advanced information about the build

6 system.	6 system.

7	7

8 If you're new to Chromium development, read the	8 If you're new to Chromium development, read the

9 [getting started guides](https://www.chromium.org/developers/how-tos/get-the-cod e).	9 [getting started guides](https://www.chromium.org/developers/how-tos/get-the-cod e).

10	10

11 There is some additional documentation on	11 There is some additional documentation on

12 [setting GYP build parameters](http://dev.chromium.org/developers/gyp-environmen t-variables).	12 [setting GYP build parameters](https://dev.chromium.org/developers/gyp-environme nt-variables).

13	13

14 [TOC]	14 [TOC]

15	15

16 ## Faster Builds	16 ## Faster Builds

17	17

18 ### Components Build	18 ### Components Build

19	19

20 A non-standard build configuration is to use dynamic linking instead of static	20 A non-standard build configuration is to use dynamic linking instead of static

21 linking for the various modules in the Chromium codebase. This results in	21 linking for the various modules in the Chromium codebase. This results in

22 significantly faster link times, but is a divergence from what is shipped and	22 significantly faster link times, but is a divergence from what is shipped and

23 primarily tested. To enable the	23 primarily tested. To enable the

24 [component build](http://www.chromium.org/developers/how-tos/component-build):	24 [component build](https://www.chromium.org/developers/how-tos/component-build):

25	25

26 $ GYP_DEFINES="component=shared_library" gclient runhooks	26 $ GYP_DEFINES="component=shared_library" gclient runhooks

27	27

28 or	28 or

29	29

30 ```	30 ```

31 C:\...\src>set GYP_DEFINES=component=shared_library	31 C:\...\src>set GYP_DEFINES=component=shared_library

32 C:\...\src>gclient runhooks	32 C:\...\src>gclient runhooks

33 ```	33 ```

34	34

(...skipping 114 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
149	149

150 $ GYP_DEFINES="branding=Chrome buildtype=Official" gclient runhooks	150 $ GYP_DEFINES="branding=Chrome buildtype=Official" gclient runhooks

151	151

152 Then building the `chrome` target will produce the official build. This tip can	152 Then building the `chrome` target will produce the official build. This tip can

153 be used in conjunction with changing the output directory, since changing these	153 be used in conjunction with changing the output directory, since changing these

154 defines will rebuild the world.	154 defines will rebuild the world.

155	155

156 Also note that some GYP\_DEFINES flags are incompatible with the official build.	156 Also note that some GYP\_DEFINES flags are incompatible with the official build.

157 If you get an error when you try to build, try removing all your flags and start	157 If you get an error when you try to build, try removing all your flags and start

158 with just the above ones.	158 with just the above ones.

OLD	NEW