Get gn analyze to respect changes to vs_toolchain.py

tools/gn/analyzer.cc

Index: tools/gn/analyzer.cc
diff --git a/tools/gn/analyzer.cc b/tools/gn/analyzer.cc
index 559287ef20ba418218ced85cb48965456e22895b..48f840751244203d47bae63c276fb8811ecd2895 100644
--- a/tools/gn/analyzer.cc
+++ b/tools/gn/analyzer.cc
@@ -59,7 +59,8 @@ LabelSet LabelsFor(const TargetSet& targets) {
 bool AnyBuildFilesWereModified(const SourceFileSet& source_files) {
   for (auto* file : source_files) {
     if (base::EndsWith(file->value(), ".gn", base::CompareCase::SENSITIVE) ||
-        base::EndsWith(file->value(), ".gni", base::CompareCase::SENSITIVE))
+        base::EndsWith(file->value(), ".gni", base::CompareCase::SENSITIVE) ||
+        file->GetName() == "vs_toolchain.py")

[brettw, 2017/03/29 23:05:07]

I notice there are three such files:
 //v8/gypfiles/vs_toolchain.py
 //build/vs_toolchain.py
 //third_party/boringssl/src/util/bot/vs_toolchain.py
and only one of them counts. If boringssl rolls and we get an updated version of
it's toolchain file, it sort of sucks to rebuild all. Is there a more precise
way to specify this? Not a huge deal if it's hard.

       return true;
   }
   return false;
@@ -262,7 +263,7 @@ std::string Analyzer::Analyze(const std::string& input, Err* err) const {
 
   // TODO(crbug.com/555273): We can do smarter things when we detect changes
   // to build files. For example, if all of the ninja files are unchanged,
-  // we know that we can ignore changes to these files. Also, for most .gn
+  // we know that we can ignore changes to .gn* files. Also, for most .gn
   // files, we can treat a change as simply affecting every target, config,
   // or toolchain defined in that file.
   if (AnyBuildFilesWereModified(inputs.source_files)) {