diff options
| author | torne@chromium.org <torne@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-31 09:25:47 +0000 |
|---|---|---|
| committer | torne@chromium.org <torne@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-31 09:25:47 +0000 |
| commit | 31a46dfacc2c4e856f81ab6bbe6dbb2b6127333e (patch) | |
| tree | afb551639537fc4264a2e30b40a71415f8e7ce16 /build/all.gyp | |
| parent | b6b90fed5146f71f39757249b00bfa3b9f40ac02 (diff) | |
| download | chromium_src-31a46dfacc2c4e856f81ab6bbe6dbb2b6127333e.zip chromium_src-31a46dfacc2c4e856f81ab6bbe6dbb2b6127333e.tar.gz chromium_src-31a46dfacc2c4e856f81ab6bbe6dbb2b6127333e.tar.bz2 | |
The LASTCHANGE file is created and updated by gclient runhooks under
normal circumstances, so it makes more sense to treat it as if it were a
checked-in source file, not a generated file. The rule for its
generation was still getting run once on a clean build, because the
other targets that depended on it expected a gyp timestamp file to exist
for the target.
There's no need for any other targets to actually depend on lastchange
(and in fact several of the targets that make use of the file already
don't depend on the target); it should already exist, and if it doesn't
then the source checkout is probably broken (as the other steps in
runhooks are also mandatory). So, remove the rule entirely.
Review URL: https://chromiumcodereview.appspot.com/10388213
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139765 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build/all.gyp')
| -rw-r--r-- | build/all.gyp | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/build/all.gyp b/build/all.gyp index 753edd3..0f8ef6a 100644 --- a/build/all.gyp +++ b/build/all.gyp @@ -56,7 +56,6 @@ '../v8/tools/gyp/v8.gyp:*', '../webkit/support/webkit_support.gyp:*', '../webkit/webkit.gyp:*', - 'util/build_util.gyp:*', 'temp_gyp/googleurl.gyp:*', '<(libjpeg_gyp_path):*', ], |