| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Various tweaks to make ninja happy with our gyp files.
ninja iOS builds don't CODE_SIGN yet.
ninja only supports i386/simulator for now.
pass parent_generator to mac_build.gypi for iOS sub-ninja builds
BUG=236517
Review URL: https://chromiumcodereview.appspot.com/14577007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198084 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
| |
NOTRY=true
Review URL: https://codereview.chromium.org/12946003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@189408 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
The mac_build.gypi is used to build Mac targets via ninja. The template runs gyp_chromium to generate a ninja project file, then gyp target that includes the template should include an action to run ninja for the desired targets.
BUG=None
Review URL: https://chromiumcodereview.appspot.com/10826169
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150357 0039d316-1c4b-4281-b951-d872f2087c98
|
