summaryrefslogtreecommitdiffstats
path: root/build/json_schema_compile.gypi
diff options
context:
space:
mode:
authorcjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-04-04 09:35:50 +0000
committercjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-04-04 09:35:50 +0000
commitc3aae52ad4abdfbaea23891b104d5f2b4f26ab7e (patch)
tree75fed191dd14f4d3e2dd76eeabdb2b648346c207 /build/json_schema_compile.gypi
parent7efaed367a5144c072a95f340cf13b510a3f1979 (diff)
downloadchromium_src-c3aae52ad4abdfbaea23891b104d5f2b4f26ab7e.zip
chromium_src-c3aae52ad4abdfbaea23891b104d5f2b4f26ab7e.tar.gz
chromium_src-c3aae52ad4abdfbaea23891b104d5f2b4f26ab7e.tar.bz2
Add input content checking to some build scripts
Some build steps, particularly javac, have really loose input rules. I.e. javac steps are re-built when any input jar changes. Often, this leads to unnecessary rebuilds of all the following steps. Other build tools (ninja, goma), will check the contents of the inputs to a step, and if those inputs haven't changed that tool doesn't actually re-run the command for creating the output. This change brings that same benefit to some of the Android python build scripts. Particularly those that will save a significant amount of time by adding input content checks. The checking checks both the input files and the command that will be run. It compares this against a stored md5 digest. If it has not changed, then the output does not need to be recreated (though it is still touched to trigger following steps). BUG=158821 Review URL: https://chromiumcodereview.appspot.com/13432002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192265 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build/json_schema_compile.gypi')
0 files changed, 0 insertions, 0 deletions