summaryrefslogtreecommitdiffstats
path: root/Help/generator
Commit message (Collapse)AuthorAgeFilesLines
* GHS: Add note about -T and path styleFred Baksik2021-11-151-1/+4
| | | | | | | | | | | | | | | | | | | | If backslashes are used for CMAKE_GENERATOR_TOOLSET, then ctest processing will complain about COMP0010. For example: Syntax error in cmake code at C:/Users/XXX/test_bld/Tests/CTestTestfile.cmake:253 when parsing string C:\Users\XXX\bin_tools\XXX Invalid escape sequence \U Policy CMP0010 is not set: Bad variable reference syntax is an error. Run "cmake --help-policy CMP0010" for policy details. Use the cmake_policy command to set the policy and suppress this warning.
* GHS: Update BSP selection logicFred Baksik2021-11-151-0/+2
| | | | | | | | | | Selection of a BSP only needs to be performed if not set by user. Remove all the logic for printing error and status messages about BSP selection. These messages also breaks CMake tests. NOTE: If BSP selection fails then the compiler checks will result in a build error. The build error will report that the BSP does not exist.
* GHS: Update generator documentationFred Baksik2021-11-151-29/+90
| | | | Break up into different sections and add examples
* Help: De-duplicate VS instance selection documentationBrad King2021-10-293-36/+6
| | | | | Add a section to `CMAKE_GENERATOR_INSTANCE` for VS instance selection, and reference it from the corresponding sections of each VS generator.
* Help: Fix versionadded for VS 15 2017 instance selectionBrad King2021-10-291-13/+13
| | | | | | | | Support for `CMAKE_GENERATOR_INSTANCE` was added in CMake 3.11, but the possibility was mentioned in a comment in older versions, so the wrong versionadded value was used in commit c43e845d09 (Help: Add `.. versionadded` directives to generator docs, 2020-11-11, v3.20.0-rc1~476^2).
* Merge branch 'backport-3.21-vs2022' into vs2022Brad King2021-10-271-7/+2
|\
| * VS: Update Visual Studio 17 2022 generator for the Release CandidatesBrad King2021-10-271-7/+2
| | | | | | | | | | Assume this is close enough to the final release to treat as non-experimental support.
* | Merge branch 'backport-3.21-vs2022' into vs2022Brad King2021-10-191-2/+2
|\ \ | |/
| * VS: Update Visual Studio 17 2022 generator for the Release CandidateBrad King2021-10-191-2/+2
| |
* | Merge branch 'backport-3.21-vs2022' into vs2022Brad King2021-10-141-2/+2
|\ \ | |/
| * VS: Update Visual Studio 17 2022 generator for Preview 5Brad King2021-10-141-2/+2
| |
* | Merge topic 'vs2022'Brad King2021-09-161-2/+2
|\ \ | |/ | | | | | | | | | | | | b6ac10394b VS: Update Visual Studio 17 2022 generator for Preview 4 f200f4d5a7 VS: Fix managed C++ project generation for VS 2022 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6524
| * VS: Update Visual Studio 17 2022 generator for Preview 4Brad King2021-09-151-2/+2
| |
* | Merge topic 'vs2022'Brad King2021-08-251-2/+2
|\ \ | |/ | | | | | | | | | | c8ec137da7 VS: Update Visual Studio 17 2022 generator for Preview 3.1 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6480
| * VS: Update Visual Studio 17 2022 generator for Preview 3.1Brad King2021-08-251-2/+2
| | | | | | | | Issue: #22339
* | Deprecate Visual Studio 10 2010 generatorBrad King2021-07-291-1/+8
|/ | | | | Update documentation to mark the generator deprecated. Add a warning at the end of generation plus an option to turn off the warning.
* VS: Update Visual Studio 17 2022 generator for Preview 2Brad King2021-07-151-2/+2
| | | | | | In particular, update to toolset `v143`. Fixes: #22339
* Help: Document VS generator support for Intel FortranBrad King2021-06-307-14/+21
| | | | | | | 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.
* VS: Add Visual Studio 17 2022 generatorBrad King2021-06-251-0/+61
| | | | Fixes: #22339
* Help: Remove unnecessary Sphinx versionadded markup in VS toolset selectionBrad King2021-06-255-14/+21
| | | | | In a document that says "New in version 3.14", we do not need any blocks that say "New in version 3.8".
* Help: Clarify default value of CMAKE_CONFIGURATION_TYPES for NMCKyle Edwards2021-06-021-1/+3
| | | | Fixes: #22266
* Help: Fix typos and spelling in documentationJosef Angstenberger2021-05-071-1/+1
|
* Ninja Multi-Config: Run POST_BUILD when BYPRODUCTS don't overlapKyle Edwards2021-01-071-0/+31
| | | | Fixes: #21252
* Ninja Multi-Config: Add support for cross-config custom commandsKyle Edwards2020-12-151-0/+44
| | | | Co-Author: Brad King <brad.king@kitware.com>
* Help: Fix grammar in `.. versionadded` directivesNikita Nemkin2020-12-021-1/+1
| | | | Issue: #19715
* Help: Add `.. versionadded` directives to generator docsNikita Nemkin2020-11-1213-83/+156
| | | | | | | | More `.. versionadded` could be added later when the features, variables and properties relevant to each generator are properly documented. Issue: #19715
* Help: Fix documentation for Ninja Multi-Config's build.ninjaKyle Edwards2020-10-091-2/+1
|
* Xcode: Switch to the "new build system" for Xcode 12 and aboveBrad King2020-09-181-0/+3
| | | | | | | Provide an option to switch back to the original build system via `-T buildsystem=1`. Fixes: #18088
* Xcode: Add option to specify build system variantBrad King2020-09-181-2/+21
| | | | | | Extend the `-T <toolset>` option to support a `buildsystem=` field with the Xcode generator. Add a `CMAKE_XCODE_BUILD_SYSTEM` variable to inform project code about the selected build system variant.
* 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-065-0/+10
| | | | | | | Run the `Utilities/Sphinx/update_versions.py` script to add initial markup to every top-level document and find module. Issue: #19715
* Ninja: Document that Fortran support is available with Ninja 1.10+Brad King2020-04-171-5/+1
| | | | | | Ninja 1.10 was released in Jan 2020 and has the features we need to support Fortran. Replace documentation that mentions Kitware's branch with mention of Ninja 1.10+ instead.
* Help: Move Ninja Multi-Config variable details into their respective pagesKyle Edwards2020-03-261-37/+3
|
* Ninja Multi-Config: Always generate build.ninjaKyle Edwards2020-02-271-7/+8
| | | | | If CMAKE_DEFAULT_BUILD_TYPE is not specified, use the first item from CMAKE_CONFIGURATION_TYPES instead.
* Ninja Multi-Config: Remove "NMC" from variable namesKyle Edwards2020-02-271-13/+13
| | | | | | Also rename `..._DEFAULT_BUILD_FILE_CONFIG` to `..._DEFAULT_BUILD_TYPE`. These name changes make the variables meaningful for future use by other generators.
* Help: Make note of ninja -f argument in Ninja Multi-Config docsKyle Edwards2020-02-041-1/+2
|
* Help: Explain new behavior of cmake --build in Ninja Multi-ConfigKyle Edwards2020-02-041-0/+5
|
* Ninja Multi-Config: Shuffle variables aroundKyle Edwards2020-02-031-44/+62
| | | | | | Remove redundant variable CMAKE_NINJA_MULTI_CROSS_CONFIG_ENABLE. Rename other variables. Document and improve handling of error conditions.
* Ninja Multi-Config: Add variable to control configs used in cross-config buildKyle Edwards2020-01-231-0/+6
|
* Ninja Multi-Config: Add variable to control aliases in build.ninjaKyle Edwards2020-01-221-1/+10
|
* Ninja Multi-Config: Rename variable to be more consistentKyle Edwards2020-01-161-6/+6
| | | | Also make some tweaks to the documentation.
* Ninja Multi-Config: Make cross-config building opt-inKyle Edwards2020-01-101-3/+10
| | | | | | | | | | | Many users will want to use the Ninja Multi-Config generator like a traditional Visual Studio-style multi-config generator, which doesn't mix configurations - custom commands are built using target executables of the same configuration the command is for. We do not want to force these people to generate an N*N build matrix when they only need N*1, especially if they have lots of targets. Add a new variable, CMAKE_NINJA_CROSS_CONFIG_ENABLE, to opt-in to the cross-config build matrix.
* Help: Add documentation and release notes for multi-config NinjaKyle Edwards2019-12-132-1/+81
|
* Help: Document install/strip targets for Ninja/UNIX Makefiles generatorsCristian Adam2019-10-042-6/+36
|
* Merge topic 'vs-default-platform'Brad King2019-04-221-1/+2
|\ | | | | | | | | | | | | db02be85a0 VS: Provide the default platform name to project code Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3246
| * VS: Provide the default platform name to project codeBrad King2019-04-191-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The value of `CMAKE_VS_PLATFORM_NAME` is computed by Visual Studio generators based on `CMAKE_GENERATOR_PLATFORM` or some default. Prior to the VS 2019 generator, the default was always `Win32`. However, for the `Visual Studio 16 2019` generator, the default is based on the host platform. Store the default in a new `CMAKE_VS_PLATFORM_NAME_DEFAULT` variable for use by project code. This is particularly useful in toolchain files because they are allowed to set `CMAKE_GENERATOR_PLATFORM` and so `CMAKE_VS_PLATFORM_NAME` is not yet known. Of course the toolchain file author knows whether it will set `CMAKE_GENERATOR_PLATFORM`, and if not then `CMAKE_VS_PLATFORM_NAME_DEFAULT` provides the platform name that will be used. Fixes: #19177
* | Merge topic 'ghs_os_dir'Brad King2019-04-081-1/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | a1e6b414b9 GHS: Update GHS_BSP_NAME processing 266dadf868 GHS: Print status message regarding GHS_OS_DIR Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3123
| * | GHS: Print status message regarding GHS_OS_DIRFred Baksik2019-03-291-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | -- Rename platform script so it runs before initial try_compile() in project() command. -- Fix incorrect variable name GHS_OS_DIR_OPTION -- Remove unnecessary ".*" from REGEX expression for GHS_CANDIDATE_OS_DIRS -- Forward GHS_OS_DIR_OPTION to try_compile() and preserve trailing whitespace of the variable.
* | | Help: Improve documentation formatingBartosz Kosiorek2019-04-0411-25/+28
|/ /
* | GHS: Add support for GHS Multi Generator in LinuxNaren Manimohan2019-03-211-2/+2
| |
generated by cgit v0.12 at 2025-01-06 00:06:34 (GMT)