summaryrefslogtreecommitdiffstats
path: root/Help/variable/CMAKE_GENERATOR_INSTANCE.rst
Commit message (Collapse)AuthorAgeFilesLines
* VS: Add a variable to report the Visual Studio version build numberBrad King2022-12-071-0/+3
| | | | | | | | | | VS 2017 and above come with a Visual Studio Installer tool that tracks four-component Visual Studio version numbers. We already detect the VS version number because it is needed to make some generation decisions. Provide the number to projects in a `CMAKE_VS_VERSION_BUILD_NUMBER` variable so they can use it similarly. Fixes: #24230
* Help: Factor out VS Build Number components document fragmentBrad King2022-12-071-17/+1
|
* Help: Clarify version specification in CMAKE_GENERATOR_INSTANCEBrad King2022-02-151-5/+22
| | | | | | | | Improve the documentation added by commit ec8d37b3b1 (VS: Support version specification in CMAKE_GENERATOR_INSTANCE, 2021-10-26, v3.23.0-rc1~452^2~1). Fixes: #23225
* VS: Allow CMAKE_GENERATOR_INSTANCE to specify portable instanceBrad King2021-10-291-0/+6
| | | | | | | | | | Previously the `CMAKE_GENERATOR_INSTANCE` value was used only to filter the instances reported by the Visual Studio Installer tool. If the specified install location is not known to the VS Installer, but the user provided a `version=` field, check for the installation directly on disk. Fixes: #21639, #22197
* VS: Support version specification in CMAKE_GENERATOR_INSTANCEBrad King2021-10-291-1/+6
|
* VS: Parse comma-separated fields from CMAKE_GENERATOR_INSTANCEBrad King2021-10-291-1/+12
|
* Help: De-duplicate VS instance selection documentationBrad King2021-10-291-5/+16
| | | | | Add a section to `CMAKE_GENERATOR_INSTANCE` for VS instance selection, and reference it from the corresponding sections of each VS generator.
* 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
* Help: Add documentation for default generator environment variablesEicke Herbertz2019-05-221-3/+4
| | | | | | | | | | Documentation for environment variables that control the default generator selection: * CMAKE_GENERATOR * CMAKE_GENERATOR_INSTANCE * CMAKE_GENERATOR_PLATFORM * CMAKE_GENERATOR_TOOLSET
* VS: Select and save a VS 2017 instance persistentlyBrad King2017-10-191-1/+3
| | | | | | | | | | Visual Studio 2017 supports multiple instances installed on a single machine. We use the Visual Studio Installer tool to enumerate instances and select one. Once we select an instance for a given build tree, save the result in `CMAKE_GENERATOR_INSTANCE` so we can re-configure the tree with the same instance on future re-runs of CMake. Fixes: #17268
* Add infrastructure for generators to select a build tool instanceBrad King2017-10-191-0/+22
Add cache entry `CMAKE_GENERATOR_INSTANCE` to hold the instance location persistently across re-runs of CMake in a given build tree. For now we reject the option by default if explicitly set. It will be implemented on a per-generator basis. Pass the setting into try_compile project generation. Add a RunCMake.GeneratorInstance test to cover basic use cases for the option. Verify that `CMAKE_GENERATOR_INSTANCE` is empty by default, and that it is rejected when the generator does not support a user setting. Issue: #17268
generated by cgit v0.12 at 2025-09-15 21:52:13 (GMT)