| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This was accidentally broken by commit 87c762d435 (CPack: Use
cmCommandLineArgument instead of cmsys::CommandLineArguments,
2022-04-18, v3.24.0-rc1~258^2).
Fixes: #24085
|
|\ |
|
| |\
| | |
| | |
| | | |
Merge-request: !7813
|
|\ \ \
| | |/
| |/|
| | | |
Merge-request: !7813
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `remove_filename` and `replace_extension` methods compute an offset
between the whole path in a `std::string` and a part of a path in a
`std::string_view`. This is done by subtracting their `.data()`
pointers. However, C++17 adds a non-const `.data()` through which
modification of the string is allowed. This means the copy-on-write
implementation used by the pre-C++11 std::string GNU ABI must reallocate
if the string has been copied. Our subtraction then computes an offset
between two different allocations, which is undefined behavior.
The workaround in commit b3ca4f9ad1 (cm/filesystem: Work around crash
when compiled for CYGWIN/MSYS runtime, 2021-04-22, v3.21.0-rc1~271^2~2)
avoided the problem by calling the non-const `.data()` to reallocate
before constructing the `string_view`. Instead, explicitly call the
const `.data()` method on the string, which does not reallocate.
Fixes: #22090, #23328
|
|\ \
| | |
| | |
| | | |
Merge-request: !7812
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Due to CVE-2022-39253, Git 2.30.6 sets `protocol.file.allow=user` by
default. The change has also been backported to other Git versions by
distros. This breaks some of our test cases that use the file-based
protocol locally to simulate real workflows without requiring network
access. In these cases the file protocol is safe, so explicitly enable
it in the tests.
|
|\ \
| |/ |
|
| |\
| | |
| | |
| | | |
Merge-request: !7803
|
|\ \ \
| | |/
| |/|
| | | |
Merge-request: !7803
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Some projects pass a raw `-std=` flag to the compiler in the
`try_compile` project. If they do not set CMP0128 to NEW,
we should not append a `-std=` flag where we did not before
the policy was added.
Fixes: #24063
|
|\ \
| | |
| | |
| | | |
Merge-request: !7805
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
When cross-compiling for Android, the library path suffixes `/<number>/`
refer to API level specific platform libraries instead of architecture
bitness. Disable path suffix use under NDK to avoid incorrect inclusion
of API level specific libraries below the targeted API level.
Fixes: #23830
|
|\ \
| | |
| | |
| | | |
Merge-request: !7801
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In commit 00c4f488f2 (FindJNI: support Android NDK, 2022-03-18,
v3.24.0-rc1~325^2) we used `CMAKE_ANDROID_API` to check the Android API
level. However, `CMAKE_SYSTEM_VERSION` is the authoritative value.
When cross-compiling for Android, an unset `CMAKE_ANDROID_API` can
result in failure to locate JNI because the `NativeHelper` component
cannot be found. In this case, the component is falsely assumed to be
available by default (and thus required) since the comparison against an
unset `CMAKE_ANDROID_API` variable evaluates to true. Use
`CMAKE_SYSTEM_VERSION` to determine the Android API level instead.
Issue: #23830
|
|\ \
| |/ |
|
| |\
| | |
| | |
| | | |
Merge-request: !7796
|
|\ \ \
| | |/
| |/|
| | | |
Merge-request: !7796
|
| |/
| |
| |
| |
| | |
This was accidentally left out of commit c050d6a01e (string(TIMESTAMP):
add %f specifier for microseconds, 2022-01-27, v3.23.0-rc1~59^2).
|
|\ \
| | |
| | |
| | | |
Merge-request: !7781
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Parse implicit link information for this compiler to support
mixed-language linking. This was missed by commit 85749766df
(LLVMFlang: Add support for LLVM Flang, 2021-07-07, v3.24.0-rc1~86^2).
Also activate mixed-language test cases that would have caught this.
Issue: #22387
|
|\ \
| |/ |
|
| |\
| | |
| | |
| | | |
Merge-request: !7774
|
|\ \ \
| | |/
| |/|
| | | |
Merge-request: !7774
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In commit b795c96727 (CPack/NSIS: Fix uninstall command when run from
installer, 2022-03-21, v3.23.0-rc5~9^2~1) we incorrectly removed the
`_?` parameter when calling the uninstaller during installation.
This parameter is however essential for ExecWait to actually wait for
the uninstaller to finish. Without it, the uninstaller is started in
the background and installer and uninstaller run at the same time.
See https://nsis.sourceforge.io/Docs/Chapter3.html#installerusageuninstaller
Add back the `_?` parameter to fix this regression. Use another
approach to solve the problem motivating the original change.
Fixes: #24041
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
7f4cbf6594 CUDA: Add support for the two new architectures in 11.8
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7761
|
| | |
| | |
| | |
| | | |
CUDA 11.8 introduces ada ( 89 ), and hopper ( 90 ).
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
13f3382b1c Intel/IntelLLVM: Fortran has distinct "-Werror"-like flag
ab8a0a106e COMPILE_WARNING_AS_ERROR: Fix internal formatting of options table
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !7758
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Update the compiler options table added by commit 76a08cd253
(COMPILE_WARNING_AS_ERROR: Add options to treat warnings as errors,
2022-04-21, v3.24.0-rc1~173^2) to use the Intel Fortran compilers'
dedicated `-warn*` flags.
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
In commit 76a08cd253 (COMPILE_WARNING_AS_ERROR: Add options to treat
warnings as errors, 2022-04-21, v3.24.0-rc1~173^2) we formatted the
options table entries as command-line string fragments. Since they are
part of the `CMAKE_${lang}_COMPILE_OPTIONS_*` tables, they should be
formatted as `;`-separated lists of compiler options.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
e848ce21c9 CPack/IFW: Add support for QtIFW 4.4
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7750
|
|/ /
| |
| |
| | |
Fixes: #24027
|
|\ \
| |/ |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
9cdf4c9be4 gitlab-ci: update macOS jobs to use Xcode 14.0
5d2c2b2558 Tests: Update RunCMake.XcodeProject iOS cases for Xcode 14.0
12c6fec6b4 Xcode: Drop CMAKE_INTDIR= definition in Swift targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7732
|
| | | |
|
| | |
| | |
| | |
| | | |
Issue: #24011
|
|/ /
| |
| |
| |
| | |
Xcode 14.0 warns that Swift doesn't support definition values.
Therefore `CMAKE_INTDIR` is not useful to Swift sources. Drop it.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
65260d6c1e ctest: only report make-level errors when no others are found
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !7710
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In commit ab9ad2a6a0 (ctest: report make-level errors to CDash when
using launchers, 2020-09-24, v3.19.0-rc1~84^2~1) we taught CTest to
capture and report errors from the build command when using launchers.
This had the unintended side effect of reporting a separate build error containing
the full build output when the build command returns non-zero. To fix this problem,
we now only report build command errors from CTest launchers when no other
more specific build errors are found.
Fixes: #23991
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
d34e5a98b8 LLVMFlang: Add support for Windows
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7692
|
| | | |
|
|\ \ \
| | |/
| |/| |
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !7698
|
|\ \ \ \
| | |/ /
| |/| /
| |_|/
|/| |
| | |
| | |
| | |
| | | |
8fc822e13a file: Avoid strange istringstream crash in cmake.org binaries on Alpine Linux
31f158e4c8 cmStringAlgorithms: Add functions to parse strings to long long integers
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !7698
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Somehow using `istringstream` and `operator >>` to parse an integer
crashes on Alpine Linux, at least when compiled with the settings we use
for the official `cmake.org` Linux binaries. Since commit fd0c285b12
(file: Fix types of the OFFSET and LIMIT arguments, 2022-01-04,
v3.23.0-rc1~133^2), this causes the `file(READ)` command to crash when
parsing its `LIMIT` or `OFFSET` argument. Parse the input string with
our dedicated helper to avoid the crash.
Fixes: #23872
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
edbdfba3f5 FindMatlab: add R2022b 9.13 version map
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7683
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
f0edac914a FindMatlab: Add MEX binary file suffix for Apple Silicon native Matlab
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7673
|