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: http://src.chromium.org/svn/trunk/src/build@19283 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

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".