summaryrefslogtreecommitdiffstats
path: root/build/common.gypi
diff options
context:
space:
mode:
authormmoss@chromium.org <mmoss@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-06-25 20:50:30 +0000
committermmoss@chromium.org <mmoss@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-06-25 20:50:30 +0000
commit569a274a7644fc5afb86ec49fef7a2a78b8e1e41 (patch)
tree15dc42df8dde4737f1359a0442f6e568d04ade4a /build/common.gypi
parent3e34f9b81967742052e2a4f38cd22d3bc0713b95 (diff)
downloadchromium_src-569a274a7644fc5afb86ec49fef7a2a78b8e1e41.zip
chromium_src-569a274a7644fc5afb86ec49fef7a2a78b8e1e41.tar.gz
chromium_src-569a274a7644fc5afb86ec49fef7a2a78b8e1e41.tar.bz2
Add a gyp "buildtype" variable to differentiate official release builds.
This notion was previously overloaded on "branding", but as implied, that variable should really just control the "Google Chrome" vs. "Chromium" branding. We need a separate setting to distinguish between "release" builds (which get special handling, like breakpad symbol processing), and "everyday" builds, like the buildbot continuous builds or personal developer builds. This fixes a problem where the "Google Chrome" continuous builder was unnecessarily trying to upload breakpad symbols for every single build. Review URL: http://codereview.chromium.org/132038 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19283 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build/common.gypi')
-rw-r--r--build/common.gypi10
1 files changed, 10 insertions, 0 deletions
diff --git a/build/common.gypi b/build/common.gypi
index ea21eaa..ecc896a 100644
--- a/build/common.gypi
+++ b/build/common.gypi
@@ -26,6 +26,16 @@
# Override branding to select the desired branding flavor.
'branding%': 'Chromium',
+ # Override buildtype to select the desired build flavor.
+ # Dev - everyday build for development/testing
+ # Official - release build (generally implies additional processing)
+ # TODO(mmoss) Once 'buildtype' is fully supported (e.g. Windows gyp
+ # conversion is done), some of the things which are now controlled by
+ # 'branding', such as symbol generation, will need to be refactored based
+ # on 'buildtype' (i.e. we don't care about saving symbols for non-Official
+ # builds).
+ 'buildtype%': 'Dev',
+
# Set to 1 to enable code coverage. In addition to build changes
# (e.g. extra CFLAGS), also creates a new target in the src/chrome
# project file called "coverage".