| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
0a5aeaf302 cmCTestRunTest: Consolidate test timeout selection logic
426e38cc10 cmCTestRunTest: Adopt decision for starting cmProcess timer
59336b29bd cmCTestRunTest: Remove unnecessary arguments to ForkProcess
07b5087ba7 Help: Document meaning of TIMEOUT test property with value 0
3edf7fbb41 ctest: Fix TIMEOUT test property with value 0 with --timeout flag
39a20a56dd Tests: Move `CTestTestZeroTimeout` into `RunCMake.CTestTimeout`
cd4038fe94 cmCTestTestHandler: Use in-class initialization of properties and results
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8455
|
| |
| |
| |
| |
| | |
Test timeout selection was previously spread out over several locations.
Consolidate it in a single place to make it easier to follow.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Document the behavior added by commit 51bb493574 (Test TIMEOUT property
explicitly set to zero should be honored, 2011-01-03, v2.8.4~118^2).
|
| |
| |
| |
| |
| | |
An explicit zero TIMEOUT test property value should not be overridden by
the `--timeout` flag.
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
c42630ee62 cmGeneratorExpressionNode: implement `COMPILE_ONLY` genex
0fb923c460 cmGeneratorExpressionNode: implement `COMPILE_ONLY` genex
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8411
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This generator expression is the inverse of `LINK_ONLY` and only coveys
usage requirements for the purposes of compilation. Its intended use is
to avoid needing to export targets that do not have link usage
requirements (e.g., header-only libraries) when used by another target.
See: #15415
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This generator expression is the inverse of `LINK_ONLY` and only coveys
usage requirements for the purposes of compilation. Its intended use is
to avoid needing to export targets that do not have link usage
requirements (e.g., header-only libraries) when used by another target.
It will also be used to represent private usage requirements on exported
C++ module-containing targets in the future.
Eventually there should be logic to collapse nesting of
`$<COMPILE_ONLY>` and `$<LINK_ONLY>` when generating instances of
either. A TODO is left in the code for this case.
See: #15415
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
72faa9a017 CreateRulePlaceholderExpander(): enhance memory management
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8456
|
| | |/
| |/|
| | |
| | | |
This method returns now a std::unique_ptr instance rather than a raw pointer.
|
|\ \ \ |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
587c0443cc FindCUDAToolkit: Support CUDA version extraction from version.json
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8451
|
|\ \ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
587c0443cc FindCUDAToolkit: Support CUDA version extraction from version.json
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8451
|
| |/ / /
| | | |
| | | |
| | | | |
Fixes: #24858
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
375e6fdbbe Link step: use linker dependency linker file
24a3e5cda0 cmLocalGenerator::MayBeRelativeToWorkDir: take care of all cases
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8443
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Based on work done by @ben.boeckel (!8051)
Fixes: #22217
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
202b2e1abd FindPython: Cross-reference Python_FIND_{STRATEGY,UNVERSIONED_NAMES}
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8454
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Mention each variable in the documentation of the other.
Issue: #24878
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
c64f6d5a5a Help: Document append functionality of string(JSON)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8453
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
7bf4e30090 Autogen: Default AUTOGEN_USE_SYSTEM_INCLUDE to ON if it is not set
033dc7ee2f Autogen: Add AUTOGEN_USE_SYSTEM_INCLUDE target property
8ba16db163 Tests/RunCMake: Add option for dynamic expected output
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8400
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Add policy CMP0151 to preserve the old behavior by default.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
`AUTOGEN_USE_SYSTEM_INCLUDE` was added. `AUTOGEN_USE_SYSTEM_INCLUDE`
is a boolean property that can be set on a target to indicate that the
autogen target include directory should be added as a system include
directory or normal include directory to the target.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Add `RunCMake_TEST_EXPECT_*` variables for this.
|
| |_|/ / / /
|/| | | | | |
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
272fe88ac6 Find{BLAS,LAPACK}: Add AOCL BLIS/libFLAME
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8450
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The AMD Optimizing CPU Libraries (AOCL) provide forks of BLIS and
libFLAME that are optimized for AMD "Zen" core architectures.
Closes: #23605
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
195339e7ac gitlab-ci: Add job testing Intel 2021.9.0 compilers on Windows
1b44973343 gitlab-ci: Add job testing IntelLLVM 2023.1.0 compilers on Windows
a5fd03a53d Tests: Teach CompileFeatures to tolerate __STDC_VERSION__ on Intel Classic
1b7649604e Tests: Teach RunCMake to ignore Intel Classic deprecation on Windows
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8447
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Extend commit 29e45a94b0 (Tests: Teach RunCMake to ignore Intel Classic
compiler deprecation warnings, 2022-10-03, v3.25.0-rc1~51^2~1) to cover
warnings from `icl` too.
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
967feaa435 FortranCInterface: Reuse primary detection results in VERIFY function
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8448
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since commit 14f7a043e3 (Teach FortranCInterface to load outside
results, 2009-08-24, v2.8.0~262) we support passing the detection
results into `try_compile` by forwarding `FortranCInterface_BINARY_DIR`.
Use this in `FortranCInterface_VERIFY` to avoid repeating detection.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
35566b48b4 VS: Add variables to initialize debugger-related properties
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8445
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add variables to initialize target properties `VS_DEBUGGER_COMMAND`,
`VS_DEBUGGER_COMMAND_ARGUMENTS`, `VS_DEBUGGER_ENVIRONMENT`, and
`VS_DEBUGGER_WORKING_DIRECTORY`.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
c584882b26 Help: change links to point to the env.vars, not to the cmake vars
e40d4eb644 Help: add documentation for some CMAKE_XXX_PATH env.vars
73ce0b792f Help: minor improvement for the CMAKE_PREFIX_PATH docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8444
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The documentation of the find-commands was pointing to the
cmake variables CMAKE_PREFIX_PATH, CMAKE_INCLUDE_PATH etc.
also in the section for environment variables. Now they point
to the documentation for the respective environment variables.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This patch adds basic documentation for the CMAKE_INCLUDE_PATH,
CMAKE_LIBRARY_PATH, CMAKE_PROGRAM_PATH, CMAKE_APPBUNDLE_PATH and
CMAKE_FRAMEWORK_PATH environment variables and links to the
respective cmake variables and vice versa.
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
With this patch the CMAKE_PREFIX_PATH env. var. is now mentioned
in the help for the CMAKE_PREFIX_PATH cmake var.
|