Currently, the gyp variables CC_wrapper and CXX_wrapper can be set in
the chromium.gyp_env file. However, the host compiler wrapper variable
cannot. By exposing this variable, embedders can more easily
use tools like ccache or icecream when developing for android.
BUG=471340
Review URL: https://codereview.chromium.org/1044423005
Cr-Original-Commit-Position: refs/heads/master@{#323557}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 73e65d4adbbc1cc83f7e59b2dfe60107c2dd186e
https://codereview.chromium.org/931643002 changed variable merging
behavior for environment variables and chromium.gyp_env. The new
behavior replaces variables, with the exception of GYP_DEFINES
which is instead concatenated.
This change clarifies the state of the variables to the developer
by printing values, and more accurately describes the override
behavior as 'merges with, and individual components override,'.
Review URL: https://codereview.chromium.org/993143002
Cr-Original-Commit-Position: refs/heads/master@{#320609}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: eedc9ac929470feba9b8b4899c1aad14cbb5b97b
Environment values overwrite values in chromium.gyp_env, while values in
.gyp/include.gypi are merged to environment values. The difference is
confusing.
Moreover, .gyp/include.gypi behavior is more convenient because some developers
build multiple targets (e.g. chromium, chromeos, android chrome) so they cannot
use chromium.gyp_env.
Review URL: https://codereview.chromium.org/931643002
Cr-Original-Commit-Position: refs/heads/master@{#319232}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: ce4b0d178d5ecc3b085011cd0abe146c3ba6d85b
This allows us to override the settings in common.gypi, as
well as other include files. Only accepts one string, not an
array. Limitation of gyp_helper.
BUG=
Review URL: https://codereview.chromium.org/705663002
Cr-Original-Commit-Position: refs/heads/master@{#302841}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: cec083d3e7038a5b26e5fdc2e514d404890805cb
It looks like this made win extract_build fail.
Adds the ability for devs/troopers/etc. to set 'landmines' in the tree so that
the build will selectively clobber when a builder moves over a revision with such
a change.
This cl has an basis landmines.py, and hooks the clobber mechanism to the android
build scripts.
The relevant cl which implements this for
compile.py is here: https://chromiumcodereview.appspot.com/11234013/
I'm planning to also implement an informational invocation for gclient to let devs know
about any potential landmines so they can decide if they need to clobber.
R=cmp,maruel@chromium.org
BUG=121897
Review URL: https://chromiumcodereview.appspot.com/11175016TBR=iannucci@chromium.org
Review URL: https://codereview.chromium.org/11293111
git-svn-id: http://src.chromium.org/svn/trunk/src/build@166105 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Adds the ability for devs/troopers/etc. to set 'landmines' in the tree so that
the build will selectively clobber when a builder moves over a revision with such
a change.
This cl has an basis landmines.py, and hooks the clobber mechanism to the android
build scripts.
The relevant cl which implements this for
compile.py is here: https://chromiumcodereview.appspot.com/11234013/
I'm planning to also implement an informational invocation for gclient to let devs know
about any potential landmines so they can decide if they need to clobber.
R=cmp,maruel@chromium.org
BUG=121897
Review URL: https://chromiumcodereview.appspot.com/11175016
git-svn-id: http://src.chromium.org/svn/trunk/src/build@166085 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
cwgreene
scheib
dongseong.hwang
justsomeguy
jam@chromium.org
justincohen@google.com
scottmg@chromium.org
iannucci@chromium.org
vandebo@chromium.org