| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This ensures commands can be properly aggregated by tools
processing the profiling output.
Fixes: #20946
|
|
|
|
|
|
|
|
|
| |
Allow to specify both DIRECTORY and TARGET_DIRECTORY at the same time in
`set_source_files_properties()` and `set_property(SOURCE)` commands.
Add test cases and update the documentation.
Fixes: #20932
|
| |
|
|
|
|
|
|
|
|
| |
Clarify the order in which --resource-spec-file, RESOURCE_SPEC_FILE,
and CTEST_RESOURCE_SPEC_FILE are searched, and add tests to
enforce this.
Fixes: #20914
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In commit dd8365b3f1 (Merge branch 'upstream-KWSys' into update-kwsys,
2020-04-06, v3.18.0-rc1~397^2) we imported KWSys commit `019afb6ea`
(SystemTools: Drop GetCurrentWorkingDirectory 'collapse' argument,
2020-04-03). That caused `GetCurrentWorkingDirectory` to no longer send
paths through the KWSys translation map and broke CMake's detection of
the absolute path to a build directory containing a symbolic link.
Add our own `cmSystemTools::GetCurrentWorkingDirectory` wrapper around
the KWSys method in order to restore that mapping.
Test-case-by: Ben Boeckel <ben.boeckel@kitware.com>
Issue: #16228
Fixes: #20900
|
|\
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |
| |
| | |
Fixes: #20883
|
| |
| |
| |
| | |
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.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
b284a3c764 CudaToolkit: Update for new/removed libraries in CUDA 11
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4917
|
| |/ |
|
| |
| |
| |
| |
| | |
Drop the portion of the case names that repeats the name of the
containing test.
|
|/
|
|
| |
Fixes: #20836
|
|\
| |
| |
| |
| |
| |
| |
| | |
9ae3382855 Tests: Shorten case names in RunCMake.file-GET_RUNTIME_DEPENDENCIES test
248d0570c9 Tests: Factor out RunCMake.file-GET_RUNTIME_DEPENDENCIES test
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4904
|
| |
| |
| |
| |
| | |
Now that these cases are in a dedicated test we can drop the
`file-GET_RUNTIME_DEPENDENCIES-` prefix from their name.
|
| |
| |
| |
| | |
Move the `file(GET_RUNTIME_DEPENDENCIES)` cases out of `RunCMake.install`.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
cb9fab49dd Tests: Fix CudaOnly.StaticRuntimePlusToolkit build rpath
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4901
|
| | |
|
| |
| |
| |
| | |
Move the `GENEX_EVAL` cases and friends out of `RunCMake.GeneratorExpression`.
|
| |
| |
| |
| | |
Move the `TARGET_FILE` cases and friends out of `RunCMake.GeneratorExpression`.
|
| |
| |
| |
| | |
Move the `DEVICE_LINK` cases out of `RunCMake.GeneratorExpression`.
|
| |
| |
| |
| | |
Move the `HOST_LINK` cases out of `RunCMake.GeneratorExpression`.
|
| |
| |
| |
| | |
Move the `LINK_LANG_AND_ID` cases out of `RunCMake.GeneratorExpression`.
|
| |
| |
| |
| | |
Move the `LINK_LANGUAGE` cases out of `RunCMake.GeneratorExpression`.
|
| |
| |
| |
| | |
Move the `COMPILE_LANG_AND_ID` cases out of `RunCMake.GeneratorExpression`.
|
|/
|
|
| |
Move the `COMPILE_LANGUAGE` cases out of `RunCMake.GeneratorExpression`.
|
|\
| |
| |
| |
| |
| |
| | |
877a92e968 CUDA: Add support for disabling CUDA_ARCHITECTURES
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4886
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The ability to disable adding architectures completely for packaging purposes
and cases requiring passing the architectures flags explicitly has been
requested.
Support a false value for CUDA_ARCHITECTURES and CMAKE_CUDA_ARCHITECTURES
for this purpose.
Implements #20821.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
cc02ced530 find_program: Revert "Find programs that are executable but not readable"
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4871
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The fix in commit 86e6349ef7 (find_program: Find programs that are
executable but not readable, 2020-04-04, v3.18.0-rc1~372^2) can break
existing projects that were (likely accidentally) relying on the
old behavior to find files that are readable but not executable.
Revert the fix for now. We can re-introduce it with a policy later.
Instead of reverting the test case, update it to cover the old behavior.
That can serve as a reference for testing the policy when introduced.
Fixes: #20814
Issue: #10468
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
2e7cefec03 gitlab-ci: add a cuda10.2 builder
1a2961b895 Tests: add CUDA labels to tests which are affected by CUDA
2caa7502d5 ci: support running just a set of tests with external builders
26b4cbcf93 gitlab-ci: move Makefiles Linux tests to use the package
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4877
|
| |/ |
|
|/
|
|
|
|
|
|
|
| |
Refactoring in commit 3b547e2e4b (VS: Simplify logic adding source file
C/C++ language flag to MSVC, 2020-05-15, v3.18.0-rc1~139^2~1) failed to
account for MSVC's treatment of `.C` extensions as C. Add this special
case to the logic to restore use of `-TP` for `.C` extensions.
Fixes: #20822
|
|
|
|
|
|
|
|
| |
This makes them compatible with `VS_PACKAGE_REFERENCES` and, in
particular, fixes nuget package references in combination with install
targets.
Fixes: #20764
|
|\
| |
| |
| |
| |
| |
| |
| | |
b1243201e7 CUDA: Don't RunCMake generate separable compilation tests on Clang
1b4c690543 CUDA: Throw error if CUDA_SEPARABLE_COMPILATION is ON when using Clang
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4827
|
| |
| |
| |
| |
| |
| | |
Building these targets was already previously disabled in RunCMakeTest.cmake.
Now with us throwing an error for separable compilation during generation on
Clang we also need to stop them from being generated.
|
|/
|
|
| |
Fixes: #20641
|
|\
| |
| |
| |
| |
| |
| | |
9436ad35df target_link_libraries: self-link through ALIAS is an error
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4826
|
| |
| |
| |
| | |
Fixes: #19617
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
97fa63c09b ASM: Fix preprocessor definition flags for GNU 'as' tool
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4838
|
| | |
| | |
| | |
| | | |
Fixes: #20780
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On low-resolution filesystems, `Makefile` can end up with the same
time stamp as `CMakeCache.txt`. CMake must re-run in this case to
be conservative, but that invalidates the `-nowork` cases.
Rather than trying to detect 1s filesystems, just add an option
called `CMake_TEST_FILESYSTEM_1S` that external scripts can use
to tell CMake's test suite about this.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
8aa4d51ec5 ExternalProject: Add missing release note for git update strategy
1236590507 FetchContent: Pass through CMAKE_EP_GIT_REMOTE_UPDATE_STRATEGY if set
e71c2807ba ExternalProject: Remote checkout needs to include the remote name
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4818
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Commit 0aea435aa1 (ExternalProject: Provide choice of
git update strategies, 2020-02-12) added the git update
strategies, but the CHECKOUT strategy was not handling
remote refs correctly. The local ref would be checked out
instead and no warning or error would have been emitted.
The test that should have caught this was also malformed
and did not actually move the local master branch as intended.
|