| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
The policy added by commit f90c8ab54e (VS: Select latest available
Windows SDK version by default, 2023-04-03, v3.27.0-rc1~206^2~1) applied
only when targeting Windows 10+. Apply it to older versions too.
Fixes: #25170
Issue: #16202
|
|
|
|
|
|
|
| |
Honor an explicit `version=8.1` field value regardless of the Windows
target version.
Issue: #25170
|
|
|
|
|
|
|
| |
Honor an explicit `version=` field selecting a Windows 10 SDK regardless
of the Windows target version.
Issue: #25170
|
|
|
|
|
|
|
| |
Make logic choosing between Windows 10 SDKs and the Windows 8.1 SDK
easier to follow by consolidating it in the VS 14 generator. The only
information we need from VS 15+ generators is whether the 8.1 SDK is
installed.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This was accidentally left out of commit f90c8ab54e (VS: Select latest
available Windows SDK version by default, 2023-04-03,
v3.27.0-rc1~206^2~1).
Issue: #16202
|
|\
| |
| |
| |
| |
| |
| |
| | |
88f90a72f1 file(GENERATE): Restore INPUT|CONTENT parse checking
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8694
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Refactoring in commit bff468c988 (cmFileCommand: Use cm::optional for
keyword argument presence, 2022-06-30, v3.25.0-rc1~512^2) accidentally
broke the check that the input argument is either `INPUT` or `CONTENT`.
The check is supposed to fail when arguments are passed in the wrong
order. For example:
file(GENERATE OUTPUT ...
TARGET <target>
CONTENT <content>)
Prior to this fix, the input method would be CONTENT, but because the
first parsed keyword is not `CONTENT`, `inputIsContent` would be false.
The first parsed keyword isn't INPUT either, so we would not continue
into the error condition. CMake would then try to handle this as an
input file, when there isn't one, resulting in uninitialized memory
usage and segfaults or corruption later on.
Fixes: #25169
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
b7704e8818 Help/guide/importing-exporting: Update line numbers in prose
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8691
|
| |/
| |
| |
| |
| |
| | |
These were missed in commit aef057d0e8 (Help/guide: fix
MathFunctionsTargets.cmake path in importing-exporting, 2023-05-26,
v3.27.0-rc1~39^2) when a line was added to the example code.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
efa0e2ddaf FindJNI: Update for Xcode greater than 12.1 on macOS
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8690
|
| |/
| |
| |
| |
| |
| | |
`JavaVM.framework` was removed from Xcode in version 12.2+.
Fixes: #23364
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
7f9f96151a cmList: Fix performance regression in append/prepend
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8684
|
| | |
| | |
| | |
| | | |
Fixes: #25147
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
78e7ea598d cmLocalGenerator: Fix trivial spelling error in code comment
1285fe27ff Help: Improve formatting and fix wording for ENABLE_EXPORTS
91336d061c Help: Improve formatting and cross-references for DEPENDS_EXPLICIT_ONLY
03208d9e18 Help: Fix indenting within TARGET_RUNTIME_DLLS genex docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8688
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
0d1529000d VS: Revert "Add CMake input files to ZERO_CHECK"
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8681
|
|/
|
|
|
|
|
|
|
|
|
| |
Since commit df58dbb0e9 (VS: Add CMake input files to ZERO_CHECK,
2023-03-19, v3.27.0-rc1~157^2), projects that specify the same file both
as input to `configure_file` and as the `MAIN_DEPENDENCY` of a custom
command fail to configure. Revert the change pending further
investigation. Add a test case demonstrating the problem.
Issue: #24557
Fixes: #25149
|
|\
| |
| |
| |
| |
| |
| | |
b02f3872d0 FindPython: Restore Python_SITE* values for versions below 3.10
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8672
|
|/
|
|
|
|
|
| |
Debian based distributions have a buggy sysconfig package.
So, rely on distutils.sysconfig if python version is less than 3.10.
Fixes: #25135
|
|\
| |
| |
| |
| |
| |
| |
| | |
78bbd58545 Source: Link libatomic when needed on Linux 32-bit ARM
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8663
|
|/
|
|
| |
Fixes: #25114
|
|\
| |
| |
| |
| |
| |
| | |
3ab132d86f Help: Document that if(EXISTS) requires paths to be readable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8656
|
|/
|
|
| |
Issue: #25125
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
c172eecea6 cmTarget: Restore Fortran_PREPROCESS property initialization
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8654
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix a typo from commit e522f8ca06 (cmTarget: factor out properties
initialized for target which compile, 2023-02-01, v3.27.0-rc1~577^2~13),
that broke this property.
Also update the test suite to use this upgrade as some level of
coverage.
Fixes: #25123
|
|\ \ |
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !8648
|
|\ \ \ \
| | |/ /
| |/| /
| |_|/
|/| |
| | |
| | |
| | | |
b7c871f745 ctest: Update ctest_submit for CDash behavior change
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8648
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
open.cdash.org was recently upgraded in preparation for the release of
CDash v3.2.0. This upgrade brought a change in behavior where CDash now
responds with HTTP 400 (bad request) rather than HTTP 200 (OK) for MD5
checksum mismatches during submission time.
This commit removes our usage of CURLOPT_FAILONERROR in
cmCTestSubmitHandler.cxx This was necessary to pass along the contents
of the request body ("md5 mismatch") in cases where the web server
(CDash) responds with an error status (400).
Fixes: #25121
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
0e8584c89c CTest: Fix regression in calculating test timeout
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8647
|
|/ /
| |
| |
| | |
Fixes: #25120
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
b665966933 cmComputeLinkInformation: track OBJECT library dependencies
a99b87a628 Tests/RunCMake/CXXModules: add a test for issue #25112
2870a67540 Tests/FortranOnly: add a test case for issue #25112
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8645
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In commit b6a5382217 (Ninja: depend on language module information files
directly, 2023-02-10), introduced via !8197, language-specific module
information files (`CMakeFiles/<target>.dir/<lang>Modules.json`) files
were added as real dependencies to the dyndep collation steps.
Previously, the behavior was to inform the collator of all possible
targets and search for the files manually ignoring those which did not
exist with ordering enforced by depending on the linker output of all
dependent targets. This behavior could lead to stale information being
used (e.g., if a target stops providing any targets) and also did not
reliably build everything needed on rebuilds. Afterwards, the internal
computation changed the dependency from all possible targets to an exact
set of "these targets might have modules" query, however one that did
not include `OBJECT` libraries since do not have `LinkEntry` items
internally (their objects are instead treated as source files).
As a stopgap measure, track `OBJECT` libraries in a separate list and
query them explicitly when gathering targets which may have interesting
information. Future work can add `LinkEntry` items to represent these
targets once all `LinkEntry` consumers have been audited to make sure
they are not surprised by any `OBJECT` library entries.
Fixes: #25112
|
| | |
| | |
| | |
| | |
| | | |
Add a test case for C++ `OBJECT` libraries providing modules to
consumers.
|
|/ /
| |
| |
| |
| | |
Add a test case for Fortran `OBJECT` libraries providing modules to
consumers.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
791d4fd350 FindOpenSSL: Prefer OPENSSL_ROOT_DIR only if non-empty
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8643
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit 5cc8a69867 (FindOpenSSL: Trust the user's OPENSSL_ROOT_DIR,
2023-05-17, v3.27.0-rc1~71^2) we use `OPENSSL_ROOT_DIR` whenever it is
defined, even if it is an empty string. This breaks a pattern in
existing projects that define an empty `OPENSSL_ROOT_DIR` cache entry so
that `cmake-gui` users can fill it in. Use the value only if non-empty.
Issue: #18352
|
|\ \ \
| | |/
| |/| |
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !8642
|
|\ \ \ \
| | |/ /
| |/| /
| |_|/
|/| |
| | |
| | |
| | | |
c2601d01d1 FindCUDAToolkit: Fix nvrtc_builtins library name
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robertjmaynard@gmail.com>
Merge-request: !8642
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
The lib is named `libnvrtc-builtins.so`, not `libnvrtc_builtins.so`.
Update the change from commit 2a94c762ed (FindCUDAToolkit: Add support
for CUDA::nvrtc_static, 2023-01-20, v3.26.0-rc1~55^2). Apply a fix
similar to commit 9688a8ebc2 (FindCUDAToolkit: Fix
`nvrtc_builtins_static` library name, 2023-02-03, v3.26.0-rc2~15^2).
|
|\ \
| |/ |
|
| | |
|
| | |
|