chromium-src-build/args
altimin ad4a5750d2 [headless] Embed pak file into binary.
Embed headless_lib.pak into headless chromium binary.
Also make necessary changes to ui::ResourceBundle and ui::DataPack
to make this possible.

R=alexclarke@chromium.org,skyostil@chromium.org
BUG=610673

Review-Url: https://codereview.chromium.org/1969313005
Cr-Original-Commit-Position: refs/heads/master@{#449263}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 6ed1a70ef94814ec92966802be57c3a36d71b7f9
2017-02-09 11:59:37 +00:00
..
README.txt
headless.gn [headless] Embed pak file into binary. 2017-02-09 11:59:37 +00:00

README.txt

This directory is here to hold .gni files that contain sets of GN build
arguments for given configurations.

(Currently this directory is empty because we removed the only thing here, but
this has come up several times so I'm confident we'll need this again. If this
directory is still empty by 2017, feel free to delete it. --Brett)

Some projects or bots may have build configurations with specific combinations
of flags. Rather than making a new global flag for your specific project and
adding it all over the build to each arg it should affect, you can add a .gni
file here with the variables.

For example, for project foo you may put in build/args/foo.gni:

  target_os = "android"
  use_pulseaudio = false
  use_ozone = true
  system_libdir = "foo"

Users wanting to build this configuration would run:

  $ gn args out/mybuild

And add the following line to their args for that build directory:

  import("//build/args/foo.gni")
  # You can set any other args here like normal.
  is_component_build = false

This way everybody can agree on a set of flags for a project, and their builds
stay in sync as the flags in foo.gni are modified.