diff options
Diffstat (limited to 'chrome/tools')
| -rw-r--r-- | chrome/tools/build/mac/FILES.cfg | 15 |
1 files changed, 12 insertions, 3 deletions
diff --git a/chrome/tools/build/mac/FILES.cfg b/chrome/tools/build/mac/FILES.cfg index 8a09559..535a096 100644 --- a/chrome/tools/build/mac/FILES.cfg +++ b/chrome/tools/build/mac/FILES.cfg @@ -9,27 +9,36 @@ # processed by the stage/archive scripts. The known tags are: # # filename: Name of the file in the build output directory. +# arch: List of CPU architectures for which this file should be processed +# (values are based on the strings returned by python's +# platform.architecture() function). +# Note: Mac doesn't really care about 'arch' (like Linux does) +# because binaries are packaged to support multiple architectures, +# but we still tag the files to allow consistent handling in the +# buildbot scripts. Tagging them all as both 32bit and 64bit is the +# safest bet. # buildtype: List of build types for which this file should be processed. -# -# Note, Mac doesn't tag FILES with 'arch' (like Linux does) because binaries -# are packaged to support multiple architectures. FILES = [ { 'filename': 'Chromium.app', + 'arch': ['32bit', '64bit'], 'buildtype': ['dev'], }, { 'filename': 'Google Chrome.app', + 'arch': ['32bit', '64bit'], 'buildtype': ['official'], }, { 'filename': 'Google Chrome Packaging', + 'arch': ['32bit', '64bit'], 'buildtype': ['official'], }, # Remoting Host plugin files: { 'filename': 'remoting_host_plugin.plugin', + 'arch': ['32bit', '64bit'], 'buildtype': ['dev', 'official'], }, ] |