tree e3a5d6ddc74fedacf9bf905c05e285c5120eef15
parent 6bd80e4bba1e6076b262fbfa67517ec683a144c8
author sky@chromium.org <sky@chromium.org@78cadc50-ecff-11dd-a971-7dbc132099af> 1407343265 +0000
committer sky@chromium.org <sky@chromium.org@78cadc50-ecff-11dd-a971-7dbc132099af> 1407343265 +0000

Currently I've special cased gyp* file modifications higher in the
stack. By that I mean if a gyp* file has been modified I don't run
analyze and assume everything has changed. This change adds support
for modification to gyp* files. If a gyp* file has changed it assumes
all targets in the file are modified. Similarly if an included file
has been modified all targets in the file that did the include are
considered modified. Lastly, if one of the modified files is specified
on the command line via -I the I early out and assume everything needs
to be recompiled.

BUG=109173
R=scottmg@chromium.org

Review URL: https://codereview.chromium.org/442083004

git-svn-id: http://gyp.googlecode.com/svn/trunk@1962 78cadc50-ecff-11dd-a971-7dbc132099af