chromium-src-build/args
perezju 56042b74fd Add tests for Headless Linux bot
BUG=594108

Review URL: https://codereview.chromium.org/1843623002

Cr-Original-Commit-Position: refs/heads/master@{#387563}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: b8b863a043b50ec783dc9cacd683700802a27130
2016-04-15 09:21:16 +00:00
..
bots Add tests for Headless Linux bot 2016-04-15 09:21:16 +00:00
README.txt
blimp_client.gn Update to use absolute path in instruction comments. 2016-03-08 02:34:55 +00:00
blimp_engine.gn Update blimp build bot args match build/args/blimp_engine.gn 2016-04-13 17:09:42 +00:00
headless.gn Only compile ozone_platform_headless for headless.gn. 2016-04-12 13:48:20 +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.