views:

415

answers:

3

A common mistake when configuring the compilation/linking/etc. settings in VC++ 2008 is to set them in Release but not Debug (or vice versa) rather than setting them for "All Configurations". Any suggestions on how to avoid this kind of mistake?

Some beginnings of ideas that I have:

  • Find a way to make VC++ go to the "All Configurations" settings by default when you open the property pages rather than the active (Release / Debug) settings.

  • Have a VB script that can be run (inside or outside VC++) to check the project settings and raise any inconsistencies detected.

+1  A: 

vb or js script is perfectly ok for the task. Just dont forget to teach it that some settings should differ, such as preprocessor defines, or used runtime libraries.

eugensk00
Thanks, not perfect (would prefer a preventative or automatic solution), but this is what I'll go for...
awm
It might work automatically, say, as prebuild step, when difference is detetcted it might report the difference and ask which configuration is to propagate on the other configuration(s). I assume at this point the build should be considered failed and restarted manually.
eugensk00
+1  A: 
+1  A: 

You can generate .vsproj files with CMake or Scons or similar cross platform build system.

Lazin