summaryrefslogtreecommitdiffstats
path: root/Source
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | | Genex: Fix TARGET_PROPERTY lookup scope in transitive usage requirementsBrad King2022-11-171-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When `$<TARGET_PROPERTY:tgt,prop>` is used in an `INTERFACE_*` target property for usage requirements, it may be evaluated in the context of a dependent target in another directory. Look up the `tgt` name in the directory of the target whose property holds the expression so that imported targets isolated to that directory are visible. Fixes: #24163
* | | | | | CMake Nightly Date StampKitware Robot2022-11-181-1/+1
| |/ / / / |/| | | |
* | | | | Merge topic 'vs-build-parallel'Brad King2022-11-171-2/+0
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 48db261e69 cmake --build: Use both inter- and intra-project parallelism with msbuild Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7926
| * | | | | cmake --build: Use both inter- and intra-project parallelism with msbuildBrad King2022-11-161-2/+0
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 1ab3881ec9 (cmake: Add options for parallel builds to --build mode, 2018-04-14, v3.12.0-rc1~42^2), `cmake --build --parallel` has added two options to the msbuild command line: * `/m` enables inter-project parallelism in msbuild. * `/p:CL_MPCount=1` suppresses intra-project parallelism in cl. The latter was used to avoid `O(N^2)` compilation threads on `N` processors. In practice however, projects often have many source files in a few targets, so `--parallel` actually reduces parallelism. Drop the latter option to restore intra-project parallelism. Users can always add `-- /p:CL_MPCount=1` themselves. Fixes: #20564
* | | | | Merge topic 'file-archive-zstd-compression-level'Brad King2022-11-171-7/+16
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ed519b1cba file(ARCHIVE_CREATE): Allow higher compression level for Zstd Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7924
| * | | | | file(ARCHIVE_CREATE): Allow higher compression level for ZstdAmir Masoud Abdol2022-11-161-7/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows the Zstd compression-level to be set between 0-19. I've adjusted some of the tests, and error messages to indicates the selected algorithm, and min/max of its compression-level. Fixes: #24160
* | | | | | CMake Nightly Date StampKitware Robot2022-11-171-1/+1
| |/ / / / |/| | | |
* | | | | Merge topic 'file-copy-error-path'Brad King2022-11-163-42/+80
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 89b144789d file(COPY_FILE): Report if failure occurred on input or output path 91dd7898ee Merge branch 'upstream-KWSys' into file-copy-error-path a9c659b1b6 KWSys 2022-11-15 (6c92b9b0) Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Acked-by: Ben Boeckel <ben.boeckel@kitware.com> Merge-request: !7916
| * | | | file(COPY_FILE): Report if failure occurred on input or output pathBrad King2022-11-151-4/+14
| | | | | | | | | | | | | | | | | | | | | | | | | When we know whether a failure was associated with the input or the output path, include this information in the error message.
| * | | | Merge branch 'upstream-KWSys' into file-copy-error-pathBrad King2022-11-152-38/+66
| |/ / / | | | | | | | | | | | | | | | | | | | | # By KWSys Upstream * upstream-KWSys: KWSys 2022-11-15 (6c92b9b0)
* | | | Merge topic 'cmp0141-pch-reuse'Brad King2022-11-161-2/+4
|\ \ \ \ | | |_|/ | |/| | | | | | | | | | | | | | | | | | 94164ea55e CMP0141: Fix PCH REUSE_FROM when MSVC_DEBUG_INFORMATION_FORMAT is empty Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7914
| * | | CMP0141: Fix PCH REUSE_FROM when MSVC_DEBUG_INFORMATION_FORMAT is emptyBrad King2022-11-151-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Under the policy's NEW behavior, `[CMAKE_]MSVC_DEBUG_INFORMATION_FORMAT` may be explicitly set to an empty string to tell CMake not to add any flags for this abstraction. In this case, fall back to checking the language-wide flags as we do in the OLD behavior. This revises commit 183b9a9eca (CMP0141: Fix PCH REUSE_FROM under policy NEW behavior, 2022-10-31, v3.25.0-rc3~4^2). Issue: #24106
* | | | CMake Nightly Date StampKitware Robot2022-11-161-1/+1
| |/ / |/| |
* | | Merge topic 'cmake-E-copy-t-mode'Brad King2022-11-152-7/+61
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 8d9069e5b6 cmake -E copy: Add support for -t argument Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7913
| * | | cmake -E copy: Add support for -t argumentKyle Edwards2022-11-152-7/+61
| | | | | | | | | | | | | | | | Fixes: #23543
* | | | Merge topic 'better_handling_of_build_args'Brad King2022-11-151-19/+7
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 01611f8258 cmake: --build improve detection of no build dir Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7908
| * | | | cmake: --build improve detection of no build dirRobert Maynard2022-11-141-19/+7
| |/ / / | | | | | | | | | | | | Fixes #24157
* | | | Merge topic 'top-level-command-order'Brad King2022-11-151-0/+9
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 59573bf5b9 project: Warn at top-level if `cmake_minimum_required` wasn't called 23f3dd9f7c RunCMake/project: Ignore exact line number in stderr checks Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7902
| * | | | project: Warn at top-level if `cmake_minimum_required` wasn't calledfriendlyanon2022-11-111-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The top-level project() call will now issue an AUTHOR_WARNING if it wasn't called after cmake_minimum_required(). Fixes: #24071
* | | | | CMake Nightly Date StampKitware Robot2022-11-151-1/+1
| |/ / / |/| | |
* | | | Merge topic 'profile-genex'Brad King2022-11-1424-95/+169
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4d70a94545 Profiling: Profile genex evaluation 09d7f947d6 cmGeneratorExpression: Require cmake instance 553794e987 cmake::CreateProfilingEntry: Refactor to take lambda for args Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Acked-by: alcroito <alexandru.croitor@qt.io> Merge-request: !7898
| * | | | Profiling: Profile genex evaluationKyle Edwards2022-11-112-2/+42
| | | | |
| * | | | cmGeneratorExpression: Require cmake instanceKyle Edwards2022-11-1119-59/+92
| | | | |
| * | | | cmake::CreateProfilingEntry: Refactor to take lambda for argsKyle Edwards2022-11-114-35/+36
| | | | |
* | | | | Merge topic 'msvc-19.34-cpp-modules'Brad King2022-11-141-22/+0
|\ \ \ \ \ | | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | 0e9782b336 msvc: bless MSVC 19.34 support for C++ modules as experimental Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7745
| * | | | msvc: bless MSVC 19.34 support for C++ modules as experimentalBen Boeckel2022-11-111-22/+0
| | | | | | | | | | | | | | | | | | | | Visual Studio 17.4 now contains official support for what CMake needs.
* | | | | CMake Nightly Date StampKitware Robot2022-11-141-1/+1
| | | | |
* | | | | CMake Nightly Date StampKitware Robot2022-11-131-1/+1
| | | | |
* | | | | CMake Nightly Date StampKitware Robot2022-11-121-1/+1
| |/ / / |/| | |
* | | | Merge topic 'fix-cxx20-detection'Brad King2022-11-111-5/+12
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5e7c8f44ac Ninja: Restore support for compilers not defining a C++ standard level Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Acked-by: Jaeden Amero <kitware@patater.com> Acked-by: Martin Kojtal <martin.kojtal@arm.com> Merge-request: !7896
| * | | Ninja: Restore support for compilers not defining a C++ standard levelLingkai Dong2022-11-101-5/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 386465bf83 (cmTarget: add support for C++ module fileset types, 2022-04-08, v3.25.0-rc1~624^2~7), the Ninja generator checks for C++20 support using logic that requires `CMAKE_<LANG>_STANDARD_DEFAULT` to be non-empty. On some compilers, such as ARMClang, CMake does not automatically detect and set default language standards, thus causing `HaveStandardAvailable` to raise an internal error. To fix this issue, if `CMAKE_CXX_STANDARD_DEFAULT` is empty, assume all standards to be supported instead of calling `HaveStandardAvailable`. This is consistent with how `CompileFeaturesNode::Evaluate` handles this case. Fixes: #24146
* | | | CMake Nightly Date StampKitware Robot2022-11-111-1/+1
| |/ / |/| |
* | | Merge topic 'better-file-download-failure-msg'Brad King2022-11-101-5/+9
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8c3cf2716a file(DOWNLOAD EXPECTED_HASH): better error message when download failed Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7888
| * | | file(DOWNLOAD EXPECTED_HASH): better error message when download failedAurelien Regat-Barrel2022-11-091-5/+9
| | | |
* | | | Merge topic 'marmasm-language'Brad King2022-11-1011-1/+141
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3166547cf6 ASM_MARMASM: Add support for Microsoft ARM assembler language ce4babb566 Tests: Fix ARM64 test conditions for non-VS generators Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7793
| * | | | ASM_MARMASM: Add support for Microsoft ARM assembler languageIlia K2022-11-0911-1/+141
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://learn.microsoft.com/en-us/cpp/assembler/arm/arm-assembler-reference Fixes: #23999
* | | | | Merge topic 'cmake-gui-restore-version-info'Brad King2022-11-101-3/+8
|\ \ \ \ \ | | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | ec76a9c22f cmake-gui: Restore embedded version information in Windows binary Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7895
| * | | | cmake-gui: Restore embedded version information in Windows binaryBrad King2022-11-091-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Refactoring in commit 89a1e1c1be (Build: Link w/ `OBJECT` library is OK since 3.12, 2022-08-21, v3.25.0-rc1~97^2~19) dropped the `.res` object containing this information from the `cmake-gui` link line. Restore it.
| * | | | CMake 3.25.0-rc4v3.25.0-rc4Brad King2022-11-081-1/+1
| | | | |
* | | | | CMake Nightly Date StampKitware Robot2022-11-101-1/+1
| |/ / / |/| | |
* | | | Merge topic 'file-set-file-api'Brad King2022-11-092-8/+105
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b3e9fb67bb file-api: support exporting file set information Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7867
| * | | | file-api: support exporting file set informationBen Boeckel2022-11-082-8/+105
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This includes listing the filesets themselves as well as which file set (if any) each source file is associated with. Fixes: #24128
* | | | | CMake Nightly Date StampKitware Robot2022-11-091-1/+1
| |_|/ / |/| | |
* | | | Merge topic 'use_folders_on_by_default'Brad King2022-11-082-8/+10
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d3acd22380 USE_FOLDERS: Treat as on by default Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Amir Masoud Abdol <amirmasoudabdol@icloud.com> Merge-request: !7830
| * | | | USE_FOLDERS: Treat as on by defaultJuan Ramos2022-11-082-8/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a policy to treat the `USE_FOLDERS` global property as ON by default if it is not set. Fixes: #21695
* | | | | Merge topic 'ctest_configure-S-B'Brad King2022-11-081-1/+6
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8a16a727f8 ctest_config: pass -S, -B args for log clarity Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7870
| * | | | | ctest_config: pass -S, -B args for log clarityMichael Hirsch2022-11-041-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | Fixes: #24135
* | | | | | Merge topic 'block-var-scope'Brad King2022-11-083-16/+17
|\ \ \ \ \ \ | | |_|_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 96ddcbee60 cmState: Clarify name of member tracking the active scope in a directory cb53d9309e block: Fix variable scope protection from modification by subdirectories Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7885
| * | | | | cmState: Clarify name of member tracking the active scope in a directoryBrad King2022-11-073-17/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `DirectoryEnd` member added by commit 52dbe654de (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 3f4e5e8c3d (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.
| * | | | | block: Fix variable scope protection from modification by subdirectoriesBrad King2022-11-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 3f4e5e8c3d (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 6954c8936f (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 52dbe654de (cmState: Record the end position of each directory., 2015-08-01, v3.4.0-rc1~251^2~1). Prior to commit 44a2f3f332 (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
generated by cgit v0.12 at 2025-04-22 20:36:25 (GMT)