summaryrefslogtreecommitdiffstats
path: root/Help
Commit message (Collapse)AuthorAgeFilesLines
* CMake 3.22.3v3.22.3Brad King2022-03-041-0/+9
|
* Merge branch 'release-3.21' into release-3.22Brad King2022-03-041-3/+3
|\
| * CMake 3.21.6v3.21.6Brad King2022-03-041-3/+3
| |
* | Merge branch 'doc-MSVC_TOOLSET_VERSION-v143' into release-3.22Brad King2022-02-091-0/+1
|\ \ | |/ | | | | Merge-request: !6966
| * Help: Add MSVC_TOOLSET_VERSION value for v143 toolsetHeiko Thiel2022-02-091-0/+1
| | | | | | | | | | | | This was accidentally left out of commit f01ea7e391 (MSVC: Fix MSVC_TOOLSET_VERSION for VS 2022 v143 toolset, 2019-04-03, v3.21.3~10^2~1).
* | Merge branch 'release-3.21' into release-3.22Brad King2022-02-011-0/+7
|\ \ | |/
| * CMake 3.21.5v3.21.5Brad King2022-02-011-0/+7
| |
| * Merge branch 'help-try-compile-result-var' into release-3.21Brad King2022-01-312-13/+0
| |\ | | | | | | | | | Merge-request: !6923
* | \ Merge topic 'help-try-compile-result-var' into release-3.22Brad King2022-02-012-13/+0
|\ \ \ | | |/ | |/| | | | | | | | | | | | | 34d263270e Help: Drop incorrect versionadded for try_compile result variable Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6923
| * | Help: Drop incorrect versionadded for try_compile result variablefriendlyanon2022-01-312-13/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit c705279bae (Help: Add `.. versionadded` directives to commands documentation, 2020-11-08, v3.20.0-rc1~508^2) we accidentally added ``versionadded`` markup suggesting that the first argument to `try_compile` was fixed as `RESULT_VAR` prior to CMake 3.14. This was probably due to misinterpreting the change from commit 7975edeac5 (Help: User-provided variable names for try_* commands, 2019-02-24, v3.14.0-rc3~16^2~3). The result variable has never been fixed. Drop the incorrect markup.
* | | Help: Add missing 3.22.1 section to the release notesBrad King2022-01-241-0/+7
| | | | | | | | | | | | | | | | | | 3.22.1 had no release notes because there were no changes to documented features or interfaces. Now that we have a 3.22.2 section, add one for the previous patch release to avoid confusion.
* | | CMP0128: Add flag in OLD mode even when standard matches the defaultRaul Tambre2022-01-231-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | Commit 4a0485be (cmStandardLevelResolver: Avoid unnecessary flags, fix unset level logic, 2021-04-29) unintentionally changed the behavior by modifying the code to match a pre-existing comment. The resulting behavior change however matches the intentions of CMP0128, so we simply need to guard it. Fixes #23122.
* | | Merge topic 'doc-if-basic-expressions' into release-3.22Brad King2021-12-011-4/+15
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 294581a443 Help: Be more explicit about the behavior of if(<string>) 3a9695557d Help: Explicitly state that if(ENV{some_var}) is always false Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6768
| * | | Help: Be more explicit about the behavior of if(<string>)Craig Scott2021-12-011-4/+13
| | | |
| * | | Help: Explicitly state that if(ENV{some_var}) is always falseCraig Scott2021-12-011-1/+3
| | | |
* | | | Help: Clarify CMAKE_INSTALL_MODE documentationFelix Lelchuk2021-11-231-10/+70
| | | | | | | | | | | | | | | | Fixes: #22869 Co-Authored-By: Craig Scott <craig.scott@crascit.com>
* | | | Help: Use definition list for allowed values of CMAKE_INSTALL_MODECraig Scott2021-11-231-8/+27
|/ / / | | | | | | | | | Clean up the wording as well for improved consistency and clarity.
* | | gitlab-ci: shorten job prefixesBen Boeckel2021-11-232-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This helps to maximize the amount of information visible in the GitLab web interface. Also document their meaning in the developer documentation and in the CI configuration file directly. See: https://gitlab.com/gitlab-org/gitlab/-/issues/8496
* | | Help: Suggest CMAKE_POLICY_DEFAULT_CMP0126 in CMP0126 docsBrad King2021-11-221-1/+4
| | |
* | | Help: Suggest CMAKE_POLICY_DEFAULT_CMP0077 in CMP0077 docsBrad King2021-11-221-1/+3
| | | | | | | | | | | | Issue: #20490
* | | Help: Document more use cases for CMAKE_POLICY_DEFAULT_CMPNNNNBrad King2021-11-221-6/+13
| | |
* | | Help: ENVIRONMENT_MODIFICATION path_list_... separator is based on hostCraig Scott2021-11-211-2/+4
| | | | | | | | | Fixes: #22937
* | | Help: Improve cross-referencing of test LABELS and related featuresCraig Scott2021-11-133-2/+12
| | |
* | | Help: Add missing version details for Additional Test MeasurementsCraig Scott2021-11-131-3/+10
| | |
* | | CMP0128: Enable/disable extensions if standard same as defaultRaul Tambre2021-11-111-22/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was intended to be part of the initial MR (!6177), but accidentally went missing when debugging nightly failures on less common systems. Noticed during !6711 review as the comment about this behaviour didn't match the code. Documentation for CMP0128 is updated to remove a false case and note the two cases related to this. Fixes #22224.
* | | Merge topic 'doc-CMP0128' into release-3.22Craig Scott2021-11-101-1/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8371056fbb Help: Correct inaccuracies in wording for CMP0128 Acked-by: Kitware Robot <kwrobot@kitware.com> Reviewed-by: Raul Tambre <raul@tambre.ee> Merge-request: !6711
| * | | Help: Correct inaccuracies in wording for CMP0128Craig Scott2021-11-081-1/+3
| | | |
* | | | Help: Use stronger wording in rule about preset inheritanceYonggang Luo2021-11-081-3/+3
| | | |
* | | | Merge topic 'vs-framework-version' into release-3.22Brad King2021-11-084-0/+46
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d51246c662 VS: Default TargetFrameworkVersion to v4.7.2 for VS 2022 f97f8537f3 VS: Model a default target framework e40cedddc0 cmVisualStudio10TargetGenerator: Refactor target framework selection 78782cc7dc cmGlobalVisualStudio8Generator: Refactor SetGeneratorPlatform Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6699
| * | | | VS: Model a default target frameworkBrad King2021-11-064-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add fields to the VS generator to select a target framework. Migrate the existing default for VS 12 .NET CF for Windows CE. Report the values in `CMAKE_VS_*` variables and use them for the CSharp compiler id project too. Issue: #22849
* | | | | Help: Clarify valid versus supported values for CUDA_STANDARDCraig Scott2021-11-071-5/+11
| |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CMake 3.18 added the first support for any compiler for 17 and 20, but those were recognized as valid values in earlier CMake versions even though there was no compiler that supported them. Make this distinction clear to avoid creating the impression that these standards could be usefully used before CMake 3.18. While 98 is recognized as a valid value, it also just gets treated as 03 internally. Document this behavior as well. Fixes: #22711
* | | | Merge topic 'doc-TARGET_RUNTIME_DLLS' into release-3.22Brad King2021-11-042-2/+14
|\ \ \ \ | | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | 001870d451 Help: Clarify TARGET_RUNTIME_DLLS behavior on imported targets Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Robert Maynard <robertjmaynard@gmail.com> Merge-request: !6700
| * | | Help: Clarify TARGET_RUNTIME_DLLS behavior on imported targetsBrad King2021-11-032-2/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This generator expression does not report the locations of `.dll` files on imported targets with the `UNKNWON` type, since their `IMPORTED_LOCATION` refers to the import library and not the DLL. Fixes: #22845
* | | | Help: Better explain CMAKE_<LANG>_EXTENSIONS_DEFAULTRaul Tambre2021-11-0210-19/+36
| |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Explain that this represents the compiler's default and mustn't be modified by the user. Clarify when it's used as the default. Additionally: * Add a reference to it in cmake-compile-features in text explaining the feature. * Add explanations for the default initialization by `CMAKE_<LANG>_EXTENSIONS_DEFAULT` to all `<LANG>_EXTENSIONS` pages and references to CMP0128. * Slightly reduce the wordiness of the default initialization explanations by removing an unnecessary "it is". Fixes #22828.
* | | Help: Add `versionadded` for `CPACK_RPM_REQUIRES_EXCLUDE_FROM` variableAlex Turbov2021-11-011-0/+2
| | |
* | | Help: Use lower-case names of sphinx directivesBrad King2021-11-011-2/+2
| | |
* | | 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).
* | | Help: Document that configure_file can create directoriesMarc Aldorasi2021-10-281-0/+1
| | |
* | | Merge topic 'builtin-help-versionadded' into release-3.22Brad King2021-10-281-0/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 054754359a cmRST: support `versionadded` and `versionchanged` directives Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !6667
| * | | cmRST: support `versionadded` and `versionchanged` directivesBen Boeckel2021-10-271-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes `versionadded` and `versionchanged` directives show up in `cmake --help-*` output instead of disappearing (and potentially making empty sections). Fixes: #22808
* | | | Merge topic 'doc-ENVIRONMENT_MODIFICATION' into release-3.22Brad King2021-10-271-2/+3
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | f6177f05da Help: Clarify ENVIRONMENT_MODIFICATION case sensitivity Acked-by: Kitware Robot <kwrobot@kitware.com> Reviewed-by: Ben Boeckel <ben.boeckel@kitware.com> Merge-request: !6661
| * | | | Help: Clarify ENVIRONMENT_MODIFICATION case sensitivityMichael Hirsch2021-10-261-2/+3
| |/ / /
* | | | Help: Drop 3.22 release note for VS 2022Brad King2021-10-271-4/+0
| | | | | | | | | | | | | | | | | | | | The 3.21.4 release will have full support, so it is not new to the 3.22 series anymore.
* | | | Merge branch 'backport-3.21-vs2022' into vs2022Brad King2021-10-272-10/+10
|\ \ \ \ | |/ / / |/| / / | |/ /
| * | VS: Update Visual Studio 17 2022 generator for the Release CandidatesBrad King2021-10-272-10/+10
| | | | | | | | | | | | | | | Assume this is close enough to the final release to treat as non-experimental support.
* | | Help: Fix file(INSTALL) docs w.r.t. CMAKE_INSTALL_MESSAGEArcturus Arcturus2021-10-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | In commit c9568de52c (install: Add CMAKE_INSTALL_MESSAGE variable (#13761), 2014-06-24, v3.1.0-rc1~370^2~1) we incorrectly documented that `CMAKE_INSTALL_MESSAGE` controls the status message for `file(INSTALL)`. Revert that. Fixes: #17162
* | | Help: Update 3.22 release notes for the VS 2022 Release CandidateBrad King2021-10-191-2/+2
| | |
* | | Merge branch 'backport-3.21-vs2022' into vs2022Brad King2021-10-192-4/+4
|\ \ \ | |/ /
| * | VS: Update Visual Studio 17 2022 generator for the Release CandidateBrad King2021-10-192-4/+4
| | |
* | | Help: gen expr: note that CONFIG is comma-separatedMichael Hirsch2021-10-191-2/+2
| | |
generated by cgit v0.12 at 2025-02-13 12:29:10 (GMT)