The following two scripts allow for the update and roll of the mac
toolchain (Xcode) via DEPS instead of thru an infrastructure install
script. The upload / download nature of the script follows somewhat
what Windows does with visual studio files and what Mac already does
for clang rolls.
build/package_mac_toolchain.py takes an Xcode.app directory
and packages up what the parts the Mac build uses into a tar file
and uploads it to gs://chrome-mac-sdk/
build/mac_toolchain.py runs as part of hooks, downloads
and decompresses the mac toolchain, and points system files to this
new directory with the DEVELOPER_DIR environment variable.
Setting DEVELOPER_DIR throughout gyp-ninja requires this GYP CL:
https://codereview.chromium.org/1806733002/
BUG=474373
Review URL: https://codereview.chromium.org/1759793003
Cr-Original-Commit-Position: refs/heads/master@{#383461}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 6a03a3dc9196b4474e7f5c08803f076a95055b44
For historical reasons gyp_chromium.py was launcher script
for gyp_chromium and the python logic lived in the
gyp_chromium. This change moves python code into the
.py file makes the extension-free gyp_chromium a launcher
for gyp_chromium.py.
Review URL: https://codereview.chromium.org/1216863010
Cr-Original-Commit-Position: refs/heads/master@{#342887}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 1eeaa328a6e7d621857c0026d0a2dd448dbf0f65
This is a workaround for multiprocessing on Windows. Importing in Python on
Windows doesn't search for imports that don't end in .py (and aren't
directories with an __init__.py). So, add this wrapper to avoid having
people change their command line to add a .py when running gyp_chromium.
R=dmazzoni@chromium.org
Review URL: https://codereview.chromium.org/11066021
git-svn-id: http://src.chromium.org/svn/trunk/src/build@160151 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
justincohen
bcwhite
sbc
scottmg@chromium.org
scottmg@google.com