msvs generator does not rebuild when command lines have changed

[GoogleCodeExporter]

Visual Studio normally only keeps track of changes to project properties 
(including those that affect the command-lines run) for the duration of one 
session. Nothing is kept on disk.

So for instance if you add a command line flag to a particular project. 
Visual studio will correctly understand that this project needs to be 
rebuild if you do it right away. If you exit and restart visual studio 
after having changed and saved the project, it will not detect that a 
rebuild is needed.

We can use gyp to compensate for this behavior using the following trick: 
Store a file containing the complete set of information known at gyp time 
related to each configuration of a target. Then add a dependency on that 
file to its related target. Only touch the file if the settings have 
changed.

Original issue reported on code.google.com by bradnel...@google.com on 26 Apr 2009 at 9:56

[GoogleCodeExporter]

Original comment by sgk@chromium.org on 6 Aug 2009 at 5:23

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by sgk@chromium.org on 18 Aug 2009 at 8:10

• Added labels: MSVS