chromium-src-build

История

jessicag 891a3ba53c Add support for Blimp engine metrics reporting in development. Currently there is no way of recording or reporting metrics for the Blimp engine. To collect metrics for the Blimp engine in development two things are required. First, for metrics recording and reporting to be enabled on the Blimp engine. Second, for the metrics logging to flag Blimp engine reports so they can be filtered from other linux metrics reports. These code behavior changes are currently kept between a single build arg, but are controlled via separate defines checks. These changes will allow metrics to be collected on development instances of Blimp and viewed separately from Linux builds. BUG=592757 Review URL: https://codereview.chromium.org/1765293002 Cr-Original-Commit-Position: refs/heads/master@{#380760} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: ab7a08b61e58d1a50565cb892f3402cebafbcf16		2016-03-11 22:37:09 +00:00
..
README.txt	Add readme for build/args directory.	2016-01-21 19:39:46 +00:00
blimp_client.gn	Update to use absolute path in instruction comments.	2016-03-08 02:34:55 +00:00
blimp_engine.gn	Add support for Blimp engine metrics reporting in development.	2016-03-11 22:37:09 +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.