summaryrefslogtreecommitdiffstats
path: root/Source/cmVisualStudio10ToolsetOptions.cxx
Commit message (Collapse)AuthorAgeFilesLines
* VS: Add toolset v142 CSharp flag tableBrad King2019-10-111-2/+1
| | | | | | | | | | | | | While the flag tables for C and C++ were generated from MSBuild `.xml` files, the CSharp flag tables were written by hand. Copy the `v141` flag table to use for the `v142` toolset. Remove the special case added by commit 626c51f47b (VS: Update for Visual Studio 2019 Preview 2, 2019-01-24, v3.14.0-rc1~74^2) that mapped the v142 flag table lookup to v141 since we now have the real v142 table. Fixes: #19828
* VS: Update for Visual Studio 2019 Preview 2Brad King2019-01-241-6/+16
| | | | | | The toolset is now called `v142`. Use matching flag tables. Fixes: #18834
* GlobalVisualStudio10Generator: Support non-standard toolset json flag files.Stephan Szabo2019-01-031-18/+12
| | | | | | If given a toolset that does not have an explicit mapping in cmVisualStudio10ToolsetOptions, check for a json flag file using the toolset name before trying the default toolset for the generator.
* Replace header flag tables with json readingStephan Szabo2018-11-281-73/+51
| | | | | Stop loading flag tables from header files and instead load the flag table information from json files in Templates/MSBuild/FlagTables.
* VS: Split link flag table between v140 and v141 toolsetsIan Hojnicki2017-06-281-3/+6
|
* cmVisualStudio10ToolsetOptions: Remove unused includeBrad King2017-05-301-1/+0
|
* VS: Add support for ASM_NASM languageEvgeny Fimochkin2017-02-071-0/+1
| | | | Fixes: #16469
* VS: Add flag tables for C#Michael Stürmer2016-12-011-0/+25
| | | | | | | Add these (currently unused) tables in preparation for `.csproj` generation support. Populate the tables for every version with a set of initial values that work well for me with VS 12 and VS 14. Later we may need to generate them more thoroughly from MSBuild `.xml` files.
* VS: Choose flag map based on the toolset nameDon Olmstead2016-10-251-0/+134
MSBuild interprets the `.vcxproj` content based on the `PlatformToolset` setting, so our reverse mapping needs to be based on that setting too. For VS 2010 and above, choose the flag map to match the toolset name rather than the generator VS version. Issue: #16153