- Nov 08, 2022
-
-
-
435b0c57 Help: Fix some redirects reported with sphinx linkcheck ac5295a9 Help: Fix broken external links found by sphinx linkcheck Acked-by:
Kitware Robot <kwrobot@kitware.com> Merge-request: !7876
-
1046a61c Help: clean up and clarify block() and return() Acked-by:
-
96ddcbee cmState: Clarify name of member tracking the active scope in a directory cb53d930 block: Fix variable scope protection from modification by subdirectories Acked-by:
buildbot <buildbot@kitware.com> Merge-request: !7885
-
128c414a Help: Clarify compilers affected by MSVC ABI abstractions Acked-by:
-
ed24414e FindOpenSSL: Search "lib64" for mingw 64-bit installs Acked-by:
-
beade1cb Tasking: Update CMAKE_TASKING_TOOLSET documentation Acked-by:
-
0a1d5589 Tasking: Remove CMAKE_SYSTEM_PROCESSOR support per CMP0123 Acked-by:
-
7e1a4567 Help: Make VALIDATOR wording clearer and more precise Acked-by:
-
- Nov 07, 2022
-
-
Brad King authored
The `DirectoryEnd` member added by commit 52dbe654 (cmState: Record the end position of each directory., 2015-08-01, v3.4.0-rc1~251^2~1) actually tracks the current top-most scope in a directory's stack. This is evidenced by the use case in commit 3f4e5e8c (cmState: Return end snapshot for GetBuildsystemDirectoryParent., 2015-09-01, v3.4.0-rc1~100^2~1). Rename the member to `CurrentScope` to clarify this role.
-
Brad King authored
When `cmStateSnapshot::RaiseScope` raises a variable in to a parent directory scope, it uses `GetBuildsystemDirectoryParent` to find the current top-most scope on the directory's stack. Since commit 3f4e5e8c (cmState: Return end snapshot for GetBuildsystemDirectoryParent., 2015-09-01, v3.4.0-rc1~100^2~1), that depends on the `DirectoryEnd` field in the directory's state. However, when variable-only scopes were added by commit 6954c893 (cmState: Add a VariableScope snapshot type., 2015-08-01, v3.4.0-rc1~179^2~1), we neglected to account for the addition of that field by commit 52dbe654 (cmState: Record the end position of each directory., 2015-08-01, v3.4.0-rc1~251^2~1). Prior to commit 44a2f3f3 (Add new flow-control commands for variables and policies scopes management, 2022-08-05, v3.25.0-rc1~257^2) this problem went unnoticed because there was no way to have a variable scope at the top of a directory's stack while processing a subdirectory. Now the `block()/endblock()` commands enable the behavior, so fix tracking of a variable scope as the top-most scope in a directory. Fixes: #24138
-
-
Mostly it's about replace `http:` with `https:` protocol.
-
-
Clarify the relationship between the compiler version and toolset/architecture. Fixes: #24117
-
Architecture specific compile options should be set through toolchain files. Fixes: #24115
-
-
Craig Scott authored
-
Craig Scott authored
-
- Nov 04, 2022
-
-
7e612977 Tasking: Fix PIC option for Tasking Toolset Acked-by:
Christoph Seitz <christoph.seitz@posteo.de> Merge-request: !7862
-
c50df859 VS: Restore support for two-part default toolset version Acked-by:
-
Brad King authored
-
0d3d6870 gitlab-ci: update macOS jobs to use Xcode 14.1 9684a589 Source: Replace uses of sprintf with safer snprintf in CMake 3.24 branch eea23d21 Source: Tell Git not to check whitespace in third-party curses form code Acked-by:
-
- Nov 03, 2022
-
-
Brad King authored
Merge-request: !7863
-
Brad King authored
-
Backport commit d5694e46 (Source: Replace uses of sprintf with safer snprintf, 2022-06-17, v3.25.0-rc1~587^2) to the CMake 3.24 branch. This is needed to compile without warnings using Xcode 14.1's macOS 13.0 SDK.
-
Brad King authored
-
Brad King authored
Since commit f972e4fd (cmVSGenerator: Add support for two-part toolset versions for Visual Studio, 2022-09-01, v3.25.0-rc1~180^2), if a two-part toolset version is requested, we fail early if globbing finds no auxiliary toolsets with that version. This broke our existing support for detecting when the default toolset matches the two-part version requested. Fix the logic to ignore the two-part globbing results if they are empty so we fall through to checking the default version. Fixes: #24107
-
Fixes: #24114
-
48ea2ce5 ci: Update debian10-ninja job to use Swift 5.7.1 Acked-by:
-
62f13ed5 FindCUDAToolkit: Restore usage from multiple directories Acked-by:
-
cb4e6702 Xcode: Implement Swift include directories e1ccab12 Xcode: Restore Swift framework search directories Acked-by:
-
- Nov 02, 2022
-
-
-
Brad King authored
Previously we selected a single "language for preprocessor" with which to compute both target-wide `GCC_PREPROCESSOR_DEFINITIONS` and `{HEADER,FRAMEWORK}_SEARCH_PATHS`. Since commit c0dd3dd2 (Xcode: Evaluate Swift compile definitions separately, 2022-10-25, v3.25.0-rc3~16^2) we never compute `GCC_PREPROCESSOR_DEFINITIONS` for Swift. Therefore we need to select the language for target-wide include and framework directories separately. Fixes: #24116 -
73e84a39 IAR: Restore support for CMAKE_CXX_FLAGS_INIT Acked-by:
-
Brad King authored
-
Robert Maynard authoredFixes #24119
-
- Nov 01, 2022
-
-
Prior to commit a9073db7 (IAR: update language specification detection, 2021-09-23, v3.22.0-rc1~83^2) the `--c++`/`--eec++` flags were stored in `CMAKE_IAR_CXX_FLAG` so that they would be used as part of the `CMAKE_CXX_COMPILE_OBJECT` rule variable. That commit moved the flags to `CMAKE_CXX_FLAGS`, which also broke initialization of `CMAKE_CXX_FLAGS` from `CMAKE_CXX_FLAGS_INIT`. Restore the original approach. Fixes: #24111
-
-
Brad King authored
-
