| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
To complete issue #23498
|
|
|
|
| |
Fixes: #23498
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
2aa83fa15b Dependency providers: Add find_package and FetchContent support
8a28368feb FetchContent: Don't discard non-empty SOURCE_DIR and BINARY_DIR
8ce9bb8a0c FetchContent: Don't leak internal variables
74a6ddc339 cmFindPackageCommand: Handle Makefile variable definitions more robustly
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Gerhard Olsson <gerhard.nospam@gmail.com>
Merge-request: !7276
|
| |
| |
| | |
Fixes: #22619
|
| |
| |
| |
| |
| |
| | |
In commit 8d7e80cf3d (find_* commands: add control over Windows registry
views, 2022-04-16) we added documentation that is repeated by multiple
find commands. Move it to a dedicated manual section to avoid duplication.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
a6562ff579 try_compile: Add option to skip passing platform variables
4843a37676 try_compile: Propagate platform variables in project-mode too
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7265
|
| |
| |
| |
| |
| |
| |
| | |
Add a `CMAKE_TRY_COMPILE_NO_PLATFORM_VARIABLES` variable to tell
`try_compile` not to pass platform variables to the test project.
Issue: #23219
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add policy CMP0137 to propagate both our builtin variables and those
listed by `CMAKE_TRY_COMPILE_PLATFORM_VARIABLES` to `try_compile`
whole-project builds.
Inspired-by: Alexander Neumann <Alexander.Neumann@hamburg.de>
Fixes: #23219
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a6c34b0353 project(): Add new CMAKE_PROJECT_TOP_LEVEL_INCLUDES file injection point
8aa29a1793 CMakeDetermineSystem: Remove unreachable code
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !7250
|
| | |
| | |
| | | |
Fixes: #22685
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
308b698f5d Help: Make install() example component names more consistent
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7240
|
| | |
| | |
| | |
| | |
| | |
| | | |
This commit updates the documentation so that the component examples are
specified using title case to match convention used in both the existing
`Installing Exports` section and in the "Mastering CMake" book.
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
Add a `CMAKE_WATCOM_RUNTIME_LIBRARY` variable to control the
runtime library selection. Add policy CMP0136 to switch to
in place of the old hard-coded default flags.
Fixes: #23178
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
29e31e2825 Packages: Integrate FetchContent and find_package()
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Acked-by: huangqinjin <huangqinjin@gmail.com>
Merge-request: !5688
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Allow FetchContent_MakeAvailable() to try a call to
find_package() first, or redirect a find_package() call to
FetchContent_MakeAvailable(). The user can set variables
to control which of these are allowed or tried by default.
Fixes: #21687
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
0aea13d20b Help: for message(FATAL_ERROR), document nonzero exit code
cc97725137 Help: document exit code of command cmake(1)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7175
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
a693da21f3 Help: from command:if, link to environment variables
ab2bdbaf31 Help: Cross-reference ENV operator from cmake-language(7) manual
ee4e728a69 Help: From Environment Variables section, link to cmake -E env etc
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7239
|
| |/ / |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
0c33f12a39 cmake_host_system_information(WINDOWS_REGISTRY) updates
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7229
|
| |/
| |
| |
| |
| | |
* add a cross-reference in 'get_filename_component()' documentation
* rework tests for better 32bit systems support
|
|/
|
|
| |
Fixes: #22775
|
|\
| |
| |
| |
| |
| |
| |
| | |
42f7e39789 Find: Support per call disabling of CMAKE_INSTALL_PREFIX
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !7163
|
| |
| |
| |
| | |
Fixes #23359
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
b3e1fcf20a Help: Clarify that find_package GLOBAL argument is supported in full signature
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7180
|
| |/
| |
| |
| |
| |
| | |
This was accidentally left out of the docs by commit 2f1ffa003c
(find_package: Add support for default GLOBAL imported targets,
2022-03-10).
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
d0d09aa29f FILE_SET: Make INTERFACE libraries with HEADER_SETS participate in buildsystem
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Acked-by: Gabriel Nützi <gnuetzi@gmail.com>
Merge-request: !7173
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If an INTERFACE library has HEADER_SETS, and its header sets contain
files generated by a custom command, the library needs to participate in
the buildsystem so that the files will be generated.
Fixes: #23422
|
| |/
|/|
| |
| | |
Fixes: #21240, #23367
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
f779f8c0ad FILE_SET: Forbid adding header sets to Apple FRAMEWORK libraries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kyle Edwards <kyle.edwards@kitware.com>
Merge-request: !7149
|
| |
| |
| |
| |
| |
| |
| |
| | |
The feature needs a specialized implementation to place headers
in the right place inside frameworks. To avoid silently doing
the wrong thing, make this case an error for the 3.23 series.
Issue: #23386
|
|\ \
| |/
| |
| |
| |
| |
| | |
7431759ebc Help: Fix typo in install command documentation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7140
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| | |
2f0a3d43e1 Help: Fix string(JSON ... LENGTH ...) signature
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7126
|
| |
| |
| |
| |
| | |
The list of indices and/or member names is optional, i.e., can be
empty. For example, string(JSON foo LENGTH "[0,0,0]") sets foo to 3.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Similar to GNU tar add a --touch option to the tar extract command to
skip extracting the timestamps from the files in the archive
effectively touching them as if they were just created.
Issue: #22746
|
|\ \
| |/
| |
| |
| |
| |
| | |
26caa97057 define_property(): Change constraints of INITIALIZE_FROM_VARIABLE
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7103
|
| |
| |
| |
| |
| |
| |
| | |
Remove the requirement that the variable name have a prefix while
keeping the suffix requirement. Require that the property name
contains an underscore. Update docs and tests accordingly.
Fixes: #23340
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
87c3b5e421 define_property(): Only test prefix if INITIALIZE_FROM_VARIABLE is given
9b50f221f6 Help: Update the main purpose of define_property()
e993e2c52c Help: Clean up INITIALIZE_FROM_VARIABLE define_property() option
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Acked-by: Kyle Edwards <kyle.edwards@kitware.com>
Merge-request: !7090
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
87c3b5e421 define_property(): Only test prefix if INITIALIZE_FROM_VARIABLE is given
9b50f221f6 Help: Update the main purpose of define_property()
e993e2c52c Help: Clean up INITIALIZE_FROM_VARIABLE define_property() option
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Acked-by: Kyle Edwards <kyle.edwards@kitware.com>
Merge-request: !7090
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The BRIEF_DOCS and FULL_DOCS are remnants from before the
Sphinx-based documentation when CMake's internal structures
for defining properties included fields for their documentation.
They are no longer mandatory for define_property() and haven't
been in practical use for some time. The main use of the command
has evolved to now be more about how to initialize and inherit
properties, so update the docs to reflect that change in focus.
Issue: #20698
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
INITIALIZE_FROM_VARIABLE is new in CMake 3.23, but the
versionadded note was missing in the original commit. The docs
also failed to mention that the new option only applies to target
properties.
Amends fce24e4f10 (define_property(): Add INITIALIZE_FROM_VARIABLE
argument, 2022-01-13)
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
78e0204e81 Help: Clarify when add_test and test properties support generator expressions
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7101
|
| |/
| |
| |
| | |
Issue: #23329
|
|\ \
| |/
| |
| |
| |
| |
| | |
5cb0a730c9 Help: Clarify behavior of search ignore-related variables
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7056
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not all the behaviors of CMake variables for ignoring search
locations by find_...() commands were fully documented.
Add the missing effects, clarify the wording and restructure the
way the details are assembled to reduce duplication.
Also improve the cross-referencing to ensure all the related
variables are more discoverable.
Issue: #20878
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allow find package to promote scope of imported targets by specifying
an argument to `find_package` or by specifying a CMake variable.
* Add support for CMAKE_GLOBAL_IMPORT_SCOPE variable
* Add support for GLOBAL argument to find_package
Additionally add testing for above features.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
140704d443 ctest: add option for output truncation
359e5b17d8 presets: bump version to v5
4634de335b cmCTestTestHandler: refactor CleanTestOutput method
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6993
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add `--test-output-truncation` to `ctest`. This option can be used to
customize which part of the test output is being truncated. Currently
supported values are `tail`, `middle` and `head`.
Also add equivalent `CTEST_CUSTOM_TEST_OUTPUT_TRUNCATION` variable.
Fixes: #23206
|