summaryrefslogtreecommitdiff
path: root/Help/generator/Visual Studio 14 2015.rst
Commit message (Collapse)AuthorAgeFilesLines
* Help: Replace mentions of ``-T`` and ``-A`` options with roleAlex Turbov2022-08-041-2/+2
|
* Help: Document VS generator support for Intel FortranBrad King2021-06-301-2/+3
| | | | | | | Extend the list of project types added by commit a82eb539f0 (Help: Describe the type of Visual Studio projects that can be generated, 2018-08-04, v3.13.0-rc1~227^2) to mention that Fortran projects are supported with Intel compiler integration.
* Help: Remove unnecessary Sphinx versionadded markup in VS toolset selectionBrad King2021-06-251-1/+1
| | | | | In a document that says "New in version 3.14", we do not need any blocks that say "New in version 3.8".
* Help: Add `.. versionadded` directives to generator docsNikita Nemkin2020-11-121-0/+2
| | | | | | | | More `.. versionadded` could be added later when the features, variables and properties relevant to each generator are properly documented. Issue: #19715
* VS: Add option for custom Win10 SDK version maximumjonathan molinatto2020-08-251-0/+16
| | | | | | | | | | | | | | | | | | | | | Since commit 83ddc4d289 (VS: Do not select a Windows SDK too high for current VS version, 2017-08-07, v3.13.0-rc1~72^2~2) we enforce a maximum SDK version for the VS 2015 generator. The blog post linked in the original commit is no longer available, but it can be seen here: * https://web.archive.org/web/20190108032520/https://blogs.msdn.microsoft.com/chuckw/2018/10/02/windows-10-october-2018-update/ In particular, it states: > VS 2015 Users: The Windows 10 SDK (15063, 16299, 17134, 17763) > is officially only supported for VS 2017. However, in some circumstances a higher version can be used. Add a `CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM` to override the generator's default maximum SDK version. Fixes: #20633
* Help: Add Sphinx 'versionadded' directives to each top-level documentKitware Robot2020-07-061-0/+2
| | | | | | | Run the `Utilities/Sphinx/update_versions.py` script to add initial markup to every top-level document and find module. Issue: #19715
* VS: Add support for explicit 32-bit toolset selection via host=x86Brad King2019-01-281-0/+3
| | | | | Generalize the ``host=x64`` option in `CMAKE_GENERATOR_TOOLSET` to also support ``host=x86``.
* Help: Document VS generator default platform selectionBrad King2019-01-101-0/+2
|
* Help: Suggest using -A to specify platform for VS generatorsBrad King2018-09-251-9/+18
| | | | | We already suggest `-T` for the toolset. Create a dedicated section for platform selection and suggest `-A`. Provide examples.
* Help: Describe the type of Visual Studio projects that can be generatedJean-Christophe Fillion-Robin2018-08-091-0/+6
| | | | | Issue: #17956 See-also: https://stackoverflow.com/questions/51647437/use-cmake-to-generate-visual-studio-python-projects/51666488
* VS: Provide an option to use x64 host toolsBrad King2016-10-141-0/+2
| | | | | | | | | | Visual Studio provides toolchains that are themselves built for 32-bit or 64-bit host architectures. By default it uses the 32-bit tools, but it can be told to prefer the 64-bit tools on 64-bit hosts. Extend the `CMAKE_GENERATOR_TOOLSET` specification to provide a way to request use of the 64-bit host tools. Closes: #15622
* Help: Document VS and Xcode toolset selectionBrad King2016-10-131-0/+7
| | | | | | Add explicit sections to the individual generator documentation to cover the `cmake -T` option along with the default behavior for each generator.
* Help: Clarify that `cmake -A` option sets VS IDE target architectureBrad King2016-09-301-1/+1
|
* VS: Rename VS 14 generator to 'Visual Studio 14 2015'Brad King2014-11-141-0/+16
Now that we know the year component of this VS version we can add it to the generator name. For convenience, map the name without the year to the name with the year.
View Lorry Controller Status