summaryrefslogtreecommitdiffstats
path: root/Help
Commit message (Collapse)AuthorAgeFilesLines
* CMake 3.30.7v3.30.7Brad King2025-01-231-3/+3
|
* Help: Add 3.30 release note for error on unknown arguments to ctestBrad King2024-12-171-0/+3
| | | | | | | This was left out of commit 304396d13c (ctest: Show error on invalid ctest arguments, 2024-04-03, v3.30.0-rc1~286^2). Fixes: #26539
* CMake 3.30.6v3.30.6Brad King2024-11-211-0/+7
|
* Merge branch 'release-3.29' into release-3.30Brad King2024-11-211-2/+2
|\
| * CMake 3.29.9v3.29.9Brad King2024-11-211-2/+2
| |
* | Merge topic 'doc-rel-3.29' into release-3.30Brad King2024-10-152-6/+4
|\ \ | |/ | | | | | | | | | | 0e81c12483 Help: Add 3.29 release note for try_compile LINKER_LANGUAGE option Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9905
| * Help: Add 3.29 release note for try_compile LINKER_LANGUAGE optionBrad King2024-10-152-6/+4
| | | | | | | | | | | | In commit 0f37000304 (try_{compile,run}: add LINKER_LANGUAGE option, 2023-10-12, v3.29.0-rc1~567^2) a release note was accidentally added in the wrong directory and so was not included in the 3.29 release notes.
* | CMake 3.30.5v3.30.5Brad King2024-10-081-10/+11
| |
* | project: Only check non-cache vars when setting project varsCraig Scott2024-10-072-7/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The change in commit 86ad7cc886 (project: Only define non-cache vars if already defined, 2024-09-15, v3.30.4~2^2) was meant to only check for non-cache variables when deciding whether to set non-cache project variables for the current call. However, it erroneously checked for any variable, including cache variables. This gives the intended result on the first run, but on subsequent runs a cache variable will exist that did not on the first run, leading to different behavior between the two runs. Fix the logic to only check for a pre-existing non-cache variable, as was originally intended. Fixes: #26355
* | CMake 3.30.4v3.30.4Brad King2024-09-271-9/+10
| |
* | Help: Add 3.30 release notes for project variable updatesBrad King2024-09-261-0/+17
| | | | | | | | | | | | | | Add a 3.30.3 release note for commit c1ece78d11 (project: non cache <project> prefix variables are also created, 2024-08-27, v3.30.3~2^2). Prepare a 3.30.4 release note for commit 86ad7cc886 (project: Only define non-cache vars if already defined, 2024-09-15).
* | project: Only define non-cache vars if already definedCraig Scott2024-09-201-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In c1ece78d11 (project: non cache <project> prefix variables are also created, 2024-08-27), we started explicitly setting the non-cache variable for <projectName>_SOURCE_DIR, <projectName>_BINARY_DIR, and <projectName>_IS_TOP_LEVEL in addition to setting them as cache variables. This changed the behavior when a project name was used more than once, and the second project call happens in the same scope or a child scope of the first. Previously, the first project call would set cache variables, and the second project call would not overwrite those cache variables. With the change in c1ece78d11, after the second project call the non-cache variables would mask the cache variables and the project code would see a different value to what it did before. Setting the non-cache variable was added to handle the case where a call to FetchContent_MakeAvailable() would set some non-cache variables, and it just so happened those matched the same cache variables that the project() command would set in the project being fetched. The fetched project would then see a different set of project-specific variables compared to when it was built standalone. This commit here narrows the change from c1ece78d11 such that the non-cache variable is only set by project() if there was already a non-cache variable set. This still fixes the motivating problem c1ece78d11 was intended to solve, but it avoids changing the variable values seen by a project that re-uses the same project name in related scopes. Issue: #26243, #25714 Fixes: #26281
* | Help: State valid scopes for using proj_SOURCE_DIR and proj_BINARY_DIRCraig Scott2024-09-201-2/+9
| | | | | | | | Issue: #25714
* | Help: file(CONFIGURE) only updates output file timestamp if it changesCraig Scott2024-09-061-1/+3
| |
* | CMake 3.30.3v3.30.3Brad King2024-08-291-7/+8
| |
* | Merge branch 'release-3.29' into release-3.30Brad King2024-08-291-2/+2
|\ \ | |/
| * CMake 3.29.8v3.29.8Brad King2024-08-291-2/+2
| |
* | FindPython: ensure a usable environment is set for the free threaded PythonMarc Chevrier2024-08-271-0/+8
| | | | | | | | | | | | | | | | Define the `Python_DEFINITIONS` variable for the support of free threaded Python developments on Windows. This is a complement to commit 9a0dee7257 (FindPython: Add support for free threaded python, 2024-05-30).
* | CMake 3.30.2v3.30.2Brad King2024-08-021-3/+3
| |
* | Help: Fix typo in add_test documentationBrad King2024-07-261-1/+1
| |
* | CMake 3.30.1v3.30.1Brad King2024-07-181-0/+12
| |
* | Merge branch 'release-3.29' into release-3.30Brad King2024-07-161-3/+3
|\ \ | |/
| * CMake 3.29.7v3.29.7Brad King2024-07-161-3/+3
| |
* | Help: Move deprecated modules and variables to dedicated sections權少2024-07-152-2/+2
| | | | | | | | | | | | | | These were missed in commit e0355c4ea9 (FindBoost: Add policy to remove this module, 2024-05-03, v3.30.0-rc1~150^2) and commit 0aba13a2f3 (ctest: Add explicit options for TLS server verification, 2024-03-01, v3.30.0-rc1~408^2~3).
* | Help: Fix typo in cmake-cxxmodules(7) note syntax權少2024-06-261-1/+1
| | | | | | | | | | Fix a typo from commit 5bbd2c12db (Help/cmake-cxxmodules: describe the compilation strategy, 2024-03-26, v3.30.0-rc1~251^2~22).
* | Merge topic 'link-feature-attributes-stabilization' into release-3.30Brad King2024-06-245-28/+29
|\ \ | | | | | | | | | | | | | | | | | | | | | 576567f028 Link feature attributes: stabilization 5617c34c31 Libraries processing: update configuration wording Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9607
| * | Link feature attributes: stabilizationMarc Chevrier2024-06-215-28/+29
| | | | | | | | | | | | | | | * enhance OVERRIDE handling * Update wording
* | | Help: Mention CPack/NuGet additions in the 3.30 release notesAlex Turbov2024-06-201-0/+7
| | |
* | | Merge topic 'doc-cpack-nuget' into release-3.30Brad King2024-06-191-41/+123
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | dbdca56555 Help: CPack/NuGet avoid deprecated variables in the usage example d06a39dd59 Help: CPack/NuGet add `:Supported:` to some variables a6a8212ba2 Help: CPack/NuGet add description to the added variables 039bf0f3f3 Help: CPack/NuGet fix `versionadded` position 391e339926 Help: CPack/NuGet add deprecation notes according to the current spec 4e11de312b Help: Reorder variables as they mentioned in the official spec Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9605
| * | Help: CPack/NuGet avoid deprecated variables in the usage exampleAlex Turbov2024-06-171-2/+1
| | |
| * | Help: CPack/NuGet add `:Supported:` to some variablesAlex Turbov2024-06-171-0/+9
| | | | | | | | | | | | | | | Some features of NuGet require relatively fresh versions. Mention that versions as they are specified in the upstream spec.
| * | Help: CPack/NuGet add description to the added variablesAlex Turbov2024-06-171-0/+55
| | |
| * | Help: CPack/NuGet fix `versionadded` positionAlex Turbov2024-06-171-2/+2
| | | | | | | | | | | | It should be right after `.. variable::`
| * | Help: CPack/NuGet add deprecation notes according to the current specAlex Turbov2024-06-171-0/+7
| | |
| * | Help: Reorder variables as they mentioned in the official specAlex Turbov2024-06-171-39/+51
| | | | | | | | | | | | | | | Also, group 'em into sub-sub-sections (same as in the upstream doc). See also, https://learn.microsoft.com/en-us/nuget/reference/nuspec
* | | Merge branch 'release-3.29' into release-3.30Brad King2024-06-171-0/+7
|\ \ \ | | |/ | |/|
| * | CMake 3.29.6v3.29.6Brad King2024-06-171-0/+7
| | |
* | | Help: Improve link library feature properties docsCraig Scott2024-06-154-103/+115
| |/ |/|
* | Help: Minor grammar and formatting cleanupCraig Scott2024-06-142-4/+4
| |
* | Help: Fix nuget example with unwanted comment and bad use of rst linkCraig Scott2024-06-141-3/+2
| |
* | FetchContent: Force cmake --fresh to re-execute direct population stepsCraig Scott2024-06-073-6/+21
| | | | | | | | Issue: #25468
* | Merge topic 'doc-preset-specific-macros' into release-3.30Brad King2024-06-062-3/+9
|\ \ | | | | | | | | | | | | | | | | | | 1ea780ea7c Help: Clarify preset-specific macros Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9587
| * | Help: Clarify preset-specific macrosCristian Le2024-06-062-3/+9
| | | | | | | | | | | | | | | Closes: #26030 Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
* | | Merge topic 'doc-add_subdirectory-EXCLUDE_FROM_ALL' into release-3.30Brad King2024-06-062-16/+28
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 2449c04d8d Help: improve docs for the EXCLUDE_FROM_ALL directory property Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9497
| * | | Help: improve docs for the EXCLUDE_FROM_ALL directory propertyAlex Neundorf2024-06-042-16/+28
| | | | | | | | | | | | | | | | | | | | | | | | This patch improves the wording of the documentation of the EXCLUDE_FROM_ALL directory property, and makes the add_subdirectory()- and fetchcontent-documentation refer to it.
* | | | Merge branch 'backport-3.29-cpack-wix-scope-default'Brad King2024-06-051-7/+19
|\ \ \ \ | | |_|/ | |/| |
| * | | CPack/WiX: Restore default (missing) InstallScope from 3.28 and lowerBrad King2024-06-052-8/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 60661f6770 (CPack/WiX: Make InstallScope configurable, 2023-11-07, v3.29.0-rc1~413^2) the `CPACK_WIX_INSTALL_SCOPE` default was set to `perMachine`. While installers created with `perMachine` have better behavior on their own than installers created without any `InstallScope`, they do not cleanly convert existing installations on updates. Fixes: #26029
* | | | CPack/WiX: Restore default (missing) InstallScope from 3.28 and lowerBrad King2024-06-051-3/+16
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 60661f6770 (CPack/WiX: Make InstallScope configurable, 2023-11-07, v3.29.0-rc1~413^2) the `CPACK_WIX_INSTALL_SCOPE` default was set to `perMachine`. While installers created with `perMachine` have better behavior on their own than installers created without any `InstallScope`, they do not cleanly convert existing installations on updates. Fixes: #26029
* | | Help: Drop development topic notes to prepare releaseBrad King2024-06-052-9/+0
| | | | | | | | | | | | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* | | Help: Organize and revise 3.30 release notesBrad King2024-06-051-109/+145
| | | | | | | | | | | | | | | | | | | | | | | | Add section headers similar to the 3.29 release notes and move each individual bullet into an appropriate section. Revise a few bullets. Drop the `CXX_MODULE_STD` release note since it is an experimental feature.
generated by cgit v0.12 at 2026-02-12 16:18:40 (GMT)