Changes between Version 31 and Version 32 of Guidelines/MaintenanceGuidelines


Ignore:
Timestamp:
Nov 19, 2009, 1:05:33 PM (13 years ago)
Author:
Paul A. Bristow
Comment:

editing common.js to change MS defaults.

Legend:

Unmodified
Added
Removed
Modified

  • Guidelines/MaintenanceGuidelines

    v31 v32  
    605605[http://www.geoffchappell.com/viewer.htm?doc=studies/msvc/cl/c1xx/warnings/index.htm&tx=2,27&ts=0,3820]
    606606a helpful guide to the byzantine complexity of warnings).[[BR]]
     607
     608(If you wish to make '''all''' of your VS projects in ''' all''' VS solutions compile with other options '''by default''', you might consider (carefully) editing (with a text editor, very carefully, after keeping a copy of the original) the file C:\Program Files\Microsoft Visual Studio 9.0\VC\VCWizards\1033\common.js to change from the Microsoft defaults.  This does not seem to be officially documented as far as I know.  It may save you changing the project properties repeatedly.
     609
     610{{{
     611function AddCommonConfig(oProj, strProjectName,bAddUnicode,bForEmptyProject) in the sections for debug and/or release
     612
     613CLTool.DisableLanguageExtensions = true; // add to make the default NO MS extensions.
     614
     615LinkTool.LinkIncremental = linkIncrementalNo; // add
     616
     617CLTool.WarningLevel = WarningLevel_4; // change from 3 to 4 to making the default warning level 4
     618
     619}}}
    607620
    608621'''For GCC''' this means -Wall -pendantic