Commit fd16bc44 authored by mmoss@chromium.org's avatar mmoss@chromium.org

Add 'arch' field to Mac files list for consistency on all platforms.

TEST=Fix Mac official build staging step.

Review URL: http://codereview.chromium.org/7753039

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98437 0039d316-1c4b-4281-b951-d872f2087c98
parent 041cc293
......@@ -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'],
},
]
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment