| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| | |
bbcff21f71 file(ARCHIVE*): Collapse FILES and DIRECTORY options
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4955
|
| |
| |
| |
| |
| |
| |
| |
| | |
The two options were concatenated internally for both ARCHIVE_CREATE
and ARCHIVE_EXTRACT. The distinction between files and dirs was not
meaningful. Therefore, replace them with PATHS or PATTERNS
to more accurately describe the way the options are used.
Fixes: #20884
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
e9be17ab42 Help: Update FileAPI codemodel version to 2.1, add release notes
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4956
|
|/ /
| |
| |
| | |
This fixes the documentation which should have been fixed in 9f6d40ee.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
e5f5eeca2f file: Fix CONFIGURE output relative path
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4951
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In commit a6fee09484 (file: Add CONFIGURE subcommand, 2020-03-06,
v3.18.0-rc1~584^2) we accidentally treated relative path outputs
with respect to the current working directory. Treat them with
respect to the current binary directory instead.
Fixes: #20885
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
f2c903fb9a find_library: Check that library files are readable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4945
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Refactoring in commit 6b85166920 (ENH: Refactor find_library search
logic, 2008-09-22, v2.8.0~1665) dropped a call to `FileExists` on the
path under the assumption that the presence of a file in a directory
listing means it exists. However, dropping that also dropped a check
that verifies the file is readable. Restore the `FileExists` call to
ensure that we only find readable libraries.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
95159b7dea file(ARCHIVE_CREATE): Rename TYPE option to COMPRESSION
bc45bdc819 Help: Fix contents indenting for file(ARCHIVE_...) subcommands
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4948
|
| | |
| | |
| | | |
Fixes: #20883
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
75aa3ee7e7 GoogleTest: Fix name generation for XML_OUTPUT_DIR
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4942
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Google test framework allows to write the results into an XML file
since commit e9ab39eb1d (GoogleTest: Add XML_OUTPUT_DIR parameter,
2020-03-06, v3.18.0-rc1~538^2~2). This file is passed on the command
line: `--gtest_output=xml:FILE_NAME`.
The module allows to specify a directory to save those files with
**TEST_XML_OUTPUT_PARAM**.
If the option is set, the filename will be set to
`${prefix}${pretty_suite}.${pretty_test}${suffix}.xml`.
The pretty names contain parameters for the tests, if
value-parameterized tests are used. These parameters may not be safe to
use in file names.
There are two possible options:
1. sanitize the file name
2. omit the values and use the internal numbering of gtest
This commit chose option 2. The testname needs to be a valid C++
identifier and should therefore be reasonable for a filename.
Note that the generated names contain slashes. This will lead to
subdirectories, but works on both Linux and Windows.
Fixes: #20877
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
99c8dbf497 Intel: Add flags for C++20
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4946
|
| |/
| |
| |
| |
| | |
Patch-by: Matheus Izvekov
Fixes: #20880
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
1458b4c048 Help: Add CMAKE_GTEST_DISCOVER_TESTS_DISCOVERY_MODE to release notes
642ea49115 GoogleTest: Replace SEND_ERROR with FATAL_ERROR
09c38e8de6 Tests: Don't ask for things not required for GoogleTest
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4938
|
| | | |
|
| | |
| | |
| | |
| | | |
We want to fail and halt immediately upon any error, not continue
past a fatal problem.
|
| | |
| | |
| | |
| | | |
The test cases only need C or C++, but not both. The CTest module
is also not needed because we are not running a dashboard script.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
e5ff413f41 curl: Set build options the way we need for CMake
0ef8fa5000 Merge branch 'upstream-curl' into update-curl
5717fdc114 curl 2020-06-23 (e9db32a0)
39f7cfad31 curl: Update script to get curl 7.71.0
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4937
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
* upstream-curl:
curl 2020-06-23 (e9db32a0)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Code extracted from:
https://github.com/curl/curl.git
at commit e9db32a09af03f27e86d1251a9e68e9b7486d371 (curl-7_71_0).
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f4b911a2c9 Help: Update docs for failure result of get_target_property
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4933
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
If `get_target_property` fails to find a value for a non-inherited
property, it appends `-NOTFOUND` to the var name and sets that as the
result, rather than setting the value of the var to `NOTFOUND`.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
b22586be01 VxWorks: Add Platform ID for Modules/CMakePlatformId.h.in
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4922
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
7f78bc42cb Makefile: Fix regression in .SILENT rule
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4928
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit d74e651b78 (Makefiles: Re-implement makefile target path
escaping and quoting, 2020-04-10, v3.18.0-rc1~334^2~1), `WriteMakeRule`
now correctly escapes `$` in make target paths as `$$`. However, this
caused an existing call site to escape the `$(VERBOSE)` variable
reference in the `.SILENT` prefix, making it ineffective. Sub-makefiles
are invoked with `MAKESILENT`, so this bug matters only for the `all`
target, which emits progress messages from toplevel.
Before:
# Suppress display of executed commands.
$$(VERBOSE).SILENT:
After:
# Suppress display of executed commands.
$(VERBOSE).SILENT:
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
0faa2b9870 Find{FLEX,BISON}: Add 'win-' executable names
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4931
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Distributions of these tools on Windows now use a `win-` prefix
instead of the previously-seen `win_` prefix. Search for both.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
1d9f2f9714 FindCUDA: Do not search for the deprecated nppicom when CUDA >= 11
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4929
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
The nppicom library has been removed in preference of nvjpeg starting
in CUDA 11.
Fixes: #20845
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
6c6b227813 Tests: Drop redundant FindModulesExecuteAll test
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4930
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
This test has been superseded by `CMakeOnly.AllFindModules`,
which does much more checking anyway.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
a9a258c302 try_compile: Do not try to remove '.nfs*' files
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Acked-by: Axel Huebl <axel.huebl@plasma.ninja>
Merge-request: !4913
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These files are part of the NFS implementation and should not be
removed. They will automatically disappear when NFS is done with them.
Fixes: #20844
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
b284a3c764 CudaToolkit: Update for new/removed libraries in CUDA 11
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4917
|
| |/ / / |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
a0280801f4 CUDA: Fix CMAKE_CUDA_COMPILER_TOOLKIT_ROOT detection in Visual Studio
90be0916b5 CUDA: Re-order some logic for determining the compiler
4ab5f109f0 CUDA: Remove unused variables while determining compiler
492e5f01fa CUDA: Simplify CMAKE_CUDA_COMPILER_TOOLKIT_ROOT computation
4785bd6153 CUDA: Skip the entire search for nvcc when it is CMAKE_CUDA_COMPILER
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4921
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When using a Visual Studio generator, we do not know the path to
`CMAKE_CUDA_COMPILER` until after the compiler id detection project
extracts it. However, based on the VS toolchain configuration we know
that the compiler id will be NVIDIA, so use that to drive the CUDA
architecture flag logic. After the main compiler id step we know
`CMAKE_CUDA_COMPILER`, so `CMAKE_CUDA_COMPILER_TOOLKIT_ROOT` can then be
computed.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
d9c1f05924 CUDA: Fix NVCC executable search during compiler detection
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4920
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The result variable was `CUDAToolkit_NVCC_EXECUTABLE` instead of
`_CUDA_NVCC_EXECUTABLE`, which the rest of the code used. Also, we can
simply `set()` the `_CUDA_NVCC_EXECUTABLE` value without searching.
Fixes: #20847
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
e5279c2c8f Help: Better document that CMP0105 controls DEVICE_LINK parsing
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4919
|