Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 This directory is here to hold .gni files that contain sets of GN build | |
| 2 arguments for given configurations. | |
| 3 | |
| 4 (Currently this directory is empty because we removed the only thing here, but | |
| 5 this has come up several times so I'm confident we'll need this again. If this | |
| 6 directory is still empty by 2017, feel free to delete it. --Brett) | |
| 7 | |
| 8 Some projects ro bots may have build configurations with specific combinations | |
|
tfarina
2016/01/21 19:04:50
s/ro/or?
| |
| 9 of flags. Rather than making a new global blag for your specific project and | |
|
tfarina
2016/01/21 19:04:50
s/blag/flag
| |
| 10 adding it all over the build to each arg it should affect, you can add a .gni | |
| 11 file here with the variables. | |
| 12 | |
| 13 For example, for project foo you may put in build/args/foo.gni: | |
| 14 | |
| 15 target_os = "android" | |
| 16 use_pulseaudio = false | |
| 17 use_ozone = true | |
| 18 system_libdir = "foo" | |
| 19 | |
| 20 Users wanting to build this configuration would run: | |
| 21 | |
| 22 $ gn args out/mybuild | |
| 23 | |
| 24 And add the following line to their args for that build directory: | |
| 25 | |
| 26 import("//build/args/foo.gni") | |
| 27 # You can set any other args here like normal. | |
| 28 is_component_build = false | |
| 29 | |
| 30 This way everybody can agree on a set of flags for a project, and their builds | |
| 31 stay in sync as the flags in foo.gni are modified. | |
| OLD | NEW |