diff options
| author | blundell@chromium.org <blundell@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-10-29 21:36:35 +0000 |
|---|---|---|
| committer | blundell@chromium.org <blundell@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-10-29 21:36:35 +0000 |
| commit | 5b6413f7eaf2c41cded749e442d12bb9aa24bf84 (patch) | |
| tree | 5f0a1ea0844e23bec2bd57ba8fc7e57dd3489add /breakpad | |
| parent | fea0b9617466710b4961623de0e7a34846e88cbe (diff) | |
| download | chromium_src-5b6413f7eaf2c41cded749e442d12bb9aa24bf84.zip chromium_src-5b6413f7eaf2c41cded749e442d12bb9aa24bf84.tar.gz chromium_src-5b6413f7eaf2c41cded749e442d12bb9aa24bf84.tar.bz2 | |
Specify dependences correctly when building mac tools for iOS.
Several auxiliary tools used when building Chrome for iOS are generated via the
following two-step pattern: (1) compiling the executable with ninja, and (2)
copying the executable into a location that is shared with other projects.
Previously, these two steps were specified as actions in the same target.
However, as the ordering of multiple actions in one target is defined only by
inputs and outputs and the compilation action had no inputs/outputs set, the
copying action wasn't properly depending on the compilation action.
As it's challenging to set correct inputs for the ninja build, this CL
separates these actions into two targets in order to be able to specify that
the second action should not run until the first action finishes.
Review URL: https://chromiumcodereview.appspot.com/11301003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@164743 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'breakpad')
| -rw-r--r-- | breakpad/breakpad.gyp | 25 |
1 files changed, 23 insertions, 2 deletions
diff --git a/breakpad/breakpad.gyp b/breakpad/breakpad.gyp index b121ced..e8114f4 100644 --- a/breakpad/breakpad.gyp +++ b/breakpad/breakpad.gyp @@ -718,12 +718,24 @@ ], }], [ 'OS=="ios"', { + 'variables': { + 'ninja_output_dir': 'ninja-breakpad', + 'ninja_product_dir': + '<(DEPTH)/xcodebuild/<(ninja_output_dir)/<(CONFIGURATION_NAME)', + }, + # Generation is done via two actions: (1) compiling the executable with + # ninja, and (2) copying the executable into a location that is shared + # with other projects. These actions are separated into two targets in + # order to be able to specify that the second action should not run until + # the first action finishes (since the ordering of multiple actions in + # one target is defined only by inputs and outputs, and it's impossible + # to set correct inputs for the ninja build, so setting all the inputs + # and outputs isn't an option). 'targets': [ { - 'target_name': 'breakpad_utilities', + 'target_name': 'compile_breakpad_utilities', 'type': 'none', 'variables': { - 'ninja_output_dir': 'ninja-breakpad', # Gyp to rerun 're_run_targets': [ 'breakpad/breakpad.gyp', @@ -742,6 +754,15 @@ ], 'message': 'Generating the breakpad executables', }, + ], + }, + { + 'target_name': 'breakpad_utilities', + 'type': 'none', + 'dependencies': [ + 'compile_breakpad_utilities', + ], + 'actions': [ { 'action_name': 'copy dump_syms', 'inputs': [ |