summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/VS10Project
Commit message (Collapse)AuthorAgeFilesLines
...
| * | VS: Propagate CMAKE_VS_GLOBALS into compiler id projectsAlexander Boczar2019-10-172-39/+61
| | | | | | | | | | | | Issue: #19708
| * | VS: Add support to override VCTargetsPath through toolsetAlexander Boczar2019-10-153-0/+39
| |/ | | | | | | Fixes: #19708
* | VS: Add VS_DOTNET_DOCUMENTATION_FILE propertyCharly Mourglia2019-10-153-0/+35
|/ | | | | | | Add a `VS_DOTNET_DOCUMENTATION_FILE` target property to tell VS generators to add a `DocumentationFile` setting in `.csproj` files. Fixes: #19784
* PCH: Report error when setting COMPILE_PDB_NAME propertyCristian Adam2019-10-014-0/+18
| | | | | Reusable precompile headers require specific COMPILE_PDB_NAME property values. Report error if the user tries to set a different value.
* Merge topic 'unity-build'Brad King2019-09-055-0/+126
|\ | | | | | | | | | | | | | | | | | | | | | | | | 7786a05c70 Unity build: Add XCode support 1353802af3 Unity build: Add unit tests 8dfeb5d278 Unity build: Add support for Visual Studio generator 7114c141e2 Unity build: Add support for Ninja and Makefile generators Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Stanislav Ershov <digital.stream.of.mind@gmail.com> Acked-by: Evgeniy Dushistov <dushistov@mail.ru> Acked-by: Viktor Kirilov <vik.kirilov@gmail.com> Merge-request: !3611
| * Unity build: Add unit testsCristian Adam2019-08-305-0/+126
| |
* | Precompile Headers: Fix Visual Studio 10 unit testCristian Adam2019-09-031-11/+8
|/ | | | | | The unit test is more roboust, problems like c: vs C: or having relative paths of cmake_pch.cxx instead of absolute paths.
* Merge topic 'precompile-headers'Brad King2019-08-293-0/+74
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8da78d4efe Precompile headers: Update documentation 5772930164 Precompile headers: Add unit tests 519606704e Precompile headers: Add support for Visual Studio generators 28be170fbc Precompile headers: Add support for Xcode generator b8626261e9 Precompile headers: Add methods to generate PCH sources 375d01c680 PCH: add example/test 9b6797e71d PCH: add target_precompile_headers command 0467a2f91b PCH: add PRECOMPILE_HEADERS to special properties Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Daniel Pfeifer <daniel@pfeifer-mail.de> Acked-by: Ivan171 <heavenandhell171@gmail.com> Acked-by: Stanislav Ershov <digital.stream.of.mind@gmail.com> Acked-by: Steve Mokris <smokris@softpixel.com> Acked-by: Evgeniy Dushistov <dushistov@mail.ru> Acked-by: Danila Malyutin <flashmozzg@gmail.com> Acked-by: Viktor Kirilov <vik.kirilov@gmail.com> Acked-by: Lucas Zhao <zhaopf6@163.com> Merge-request: !3553
| * Precompile headers: Add unit testsCristian Adam2019-08-283-0/+74
| |
* | VS: Add support for generator expressions to VS_CONFIGURATION_TYPEDaniel Eiband2019-08-262-2/+2
|/ | | | | | | | Generator expressions in target property VS_CONFIGURATION_TYPE might be used to set the ConfigurationType to Utility for certain configurations to not build the target while still linking to the target in other configurations. Fixes: #19613
* source_group: Improved generated filters testsMateusz Janek2019-08-169-26/+93
|
* Merge topic 'vs-spectre-off'Brad King2019-07-313-0/+42
|\ | | | | | | | | | | | | f9b7c660d7 VS: Fix mapping of `-Qspectre-` flag Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3629
| * VS: Fix mapping of `-Qspectre-` flagBrad King2019-07-303-0/+42
| | | | | | | | | | | | | | | | | | | | | | | | The mapping for this flag was added by commit 43aa632f57 (VS: Populate `-Qspectre-` flag table entry for v142, 2019-01-24, v3.14.0-rc1~74^2~7). However, it did not do anything because the special logic added by commit bb60ed6e72 (VS: Add flag table entry for -Qspectre, 2018-10-08, v3.13.0-rc1~4^2) to move the `SpectreMitigation` element from `ClCompile` to the top level only handled the presence of the setting and not its value. Extend the special logic to carry the value too. Fixes: #19535
* | Fix elseif() in place of else()Artalus2019-07-031-1/+1
| |
* | VS: Add VS_DPI_AWARE target propertyMatt Weir2019-06-266-0/+74
|/ | | | | Enables setting the visual studio project property for Manifests, controlling the DPI Aware setting.
* VS: Added support for VS package references for nugetKinan Mahdi2019-05-303-0/+44
|
* MSVC: Add support for /JMC (Just My Code)Luca Cappa2019-05-143-0/+67
|
* MSVC: Document and test behavior of empty MSVC_RUNTIME_LIBRARYBrad King2019-04-222-1/+7
| | | | | | | | Extend tests added by commit fb3370b6a1 (MSVC: Add abstraction for runtime library selection, 2019-04-10) to cover an empty value for the property. It should result in no specific setting. Issue: #19108
* Merge topic 'msvc-runtime-library'Brad King2019-04-175-0/+51
|\ | | | | | | | | | | | | | | | | | | fb3370b6a1 MSVC: Add abstraction for runtime library selection f621e7fa5d VS: Fix Fortran runtime library flag map special case for '-' options Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Ben Boeckel <ben.boeckel@kitware.com> Acked-by: Leonid Pospelov <pospelovlm@yandex.ru> Merge-request: !3211
| * MSVC: Add abstraction for runtime library selectionBrad King2019-04-175-0/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace our hard-coded defaults for `/MD` and `/MDd` with a first-class abstraction to select the runtime library from an enumeration of logical names. We've long hesitated to do this because the idea of "runtime library selection" touches on related concepts on several platforms. Avoid that scope creep by simply defining an abstraction that applies only when targeting the MSVC ABI on Windows. Removing the old default flags requires a policy because existing projects may rely on string processing to edit them and choose a runtime library under the old behavior. Add policy CMP0091 to provide compatibility. Fixes: #19108
* | VS: add target property VS_PROJECT_IMPORT_<propspath>Leonid Pospelov2019-04-153-0/+40
|/ | | | Fixes: #18998
* VS: Fix nowarn compiler option to accept warning numbers.Wil Stark2019-02-073-0/+79
| | | | | | Warning disables are transferred to the VS IDE `<NoWarn>` node. Fixes: #18878
* Merge topic 'vs-debug-utility-targets'Brad King2019-01-178-72/+84
|\ | | | | | | | | | | | | 22b43b0009 VS: Add support for VS_DEBUGGER_* properties on custom targets Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2794
| * VS: Add support for VS_DEBUGGER_* properties on custom targetsNils Gladitz2019-01-168-72/+84
| | | | | | | | | | | | Visual studio itself supports the corresponding `LocalDebugger*` properties on utility targets; support generating them from CMake as well.
* | VS: Honor target_compile_definitions for C# projectsWil Stark2019-01-163-0/+83
|/ | | | Fixes: #18698
* Restore support for a custom source group for CMakeLists.txtBrad King2019-01-143-0/+37
| | | | | | | | | | Since commit v3.11.0-rc1~467^2 (VS,Xcode: Add CMakeLists.txt sources without mutating targets, 2017-10-18) we do not add `CMakeLists.txt` to target sources but instead generate references to them directly. This accidentally dropped generation of the `.vcxproj.filters` entry for a source group in which `CMakeLists.txt` is the only member. Fixes: #18795
* VS: Fix Deploy content in .csproj filesWil Stark2018-12-073-0/+95
|
* VS: Add test for CMAKE_VS_GLOBALSMikhail Korolev2018-09-283-0/+53
|
* VS10Project: Expand VS_DEBUGGER_* capabilitiesJon Chronopoulos2018-06-179-4/+60
| | | | | This adds VS_DEBUGGER_COMMAND_ARGUMENTS and VS_DEBUGGER_ENVIRONMENT as well as allowing VS_DEBUGGER_* to use generator expressions.
* cmVisualStudio10TargetGenerator: issue warning when adding static C# libMichael Stürmer2018-05-072-0/+11
|
* Merge topic 'vs-sdk-dirs'Brad King2018-04-203-0/+100
|\ | | | | | | | | | | | | 6ec3e880e7 VS: Add variables to set SDK directories in vcxproj files Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1965
| * VS: Add variables to set SDK directories in vcxproj filesBastien Schatt2018-04-193-0/+100
| | | | | | | | | | | | | | Create `CMAKE_VS_SDK_*_DIRECTORIES` variables to tell the VS generator how to populate fields in `.vcxproj` files that specify SDK directories. Fixes: #17908
* | Merge branch 'backport-fix-explicit-CMakeLists.txt'Brad King2018-04-133-0/+31
|\ \ | |/ |/|
| * Restore support for explicitly referenced CMakeLists.txt sourcesBrad King2018-04-133-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit v3.11.0-rc1~467^2 (VS,Xcode: Add CMakeLists.txt sources without mutating targets, 2017-10-18) we do not add `CMakeLists.txt` to target sources but instead generate references to them directly. This broke projects that explicitly specify their `CMakeLists.txt` file as a source file because the explicit entry is no longer consolidated with the generated one. Teach the relevant generators to avoid duplicating `CMakeLists.txt` source references and add test cases. Fixes: #17828
* | VS: Add target property VS_DEBUGGER_COMMANDHannes Mezger2018-03-143-0/+28
| | | | | | | | Fixes: #17819
* | Replaces execute_process calls to touch files with file(TOUCH) callsShane Parris2018-02-151-2/+1
|/
* VS: Enable generation of CSharp projects without initial .cs filesMichael Stürmer2017-11-293-0/+13
| | | | fixes #17388
* Merge topic 'vs_csharp_prop_for_all_extensions'Brad King2017-06-152-15/+42
|\ | | | | | | | | | | | | c90630c5 Vs: add support for VS_CSHARP_* target property for additional file extensions Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !961
| * Vs: add support for VS_CSHARP_* target property for additional file extensionsMichael Stürmer2017-06-132-15/+42
| | | | | | | | Fixes: #16726
* | VS: add target property VS_DOTNET_REFERENCEPROP_<refname>_TAG_<tagname>Michael Stürmer2017-06-133-0/+69
|/ | | | Fixes: #16689
* VS: add test for VS_CSHARP_* source file propertyMichael Stürmer2017-03-014-0/+38
|
* VS: renamed target property VS_USER_PROPS_CXX to VS_USER_PROPSMichael Stürmer2017-01-131-1/+1
|
* VS: Add target property VS_DEBUGGER_WORKING_DIRECTORYMichael Stürmer2016-11-303-0/+28
|
* VS: Add option to customize vcxproj user props fileMichael Stürmer2016-11-294-0/+38
| | | | | | Add a `VS_USER_PROPS_CXX` target property to set the user props file of the generated `.vcxproj` file to be something other than the default `$(UserRootDir)\\Microsoft.Cpp.$(Platform).user.props`.
* Tests: Extend VS10Project to cover `.targets` file linkingSoji Yamakawa2016-11-155-0/+61
| | | | | | With VS generators for 2010 and above, passing a `.targets` file to `target_link_libraries` is expected to generate content in the `.vcxproj` file to import the targets file. Add a test to cover this.
* Revise C++ coding style using clang-formatKitware Robot2016-05-161-1/+3
| | | | | | | | | | | | | Run the `Utilities/Scripts/clang-format.bash` script to update all our C++ code to a new style defined by `.clang-format`. Use `clang-format` version 3.8. * If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content. * See the parent commit for instructions to rebase a change across this style transition commit.
* VS: Add option to set `ConfigurationType` of a .vcxproj fileFabian Otto2016-02-265-0/+33
Add a VS_CONFIGURATION_TYPE target property to set this value explicitly. This is useful to build a Windows Kernel Mode Driver, for example.