| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Also, added CAPTURE_CMAKE_ERROR to vim synax file for ctest_submit,
ctest_update and ctest_memcheck.
|
|
|
|
|
|
| |
Many existing tutorials suggest `include_directories` but that does
not handle propagation to dependencies and such. Add a link to its
documentation suggesting `target_include_directories` instead.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
30d08bdce9 doc: Consistently use <PackageName> for describing the name of a package
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2283
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
492ade276b Help: Add explicit <PackageName>_ROOT variable documentation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2225
|
| |
| |
| |
| |
| |
| | |
Add documentation for both the CMake variable and environment variable
of this name pattern. Update references to these names to link to their
documents. Clarify the pattern used to construct their names.
|
| |
| |
| |
| |
| | |
Our regex engine doesn't interpret `\`-escapes but CMake language escape
sequences may be used to pass literal whitespace characters to it.
|
|\ \
| |/
| |
| |
| |
| |
| | |
62b4df1e84 Help: Mention IMPORTED_OBJECTS in add_library docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2216
|
| |
| |
| |
| |
| |
| |
| | |
The `IMPORTED_OBJECTS` is to object libraries as `IMPORTED_LOCATION`
is to normal libraries.
Fixes: #18176
|
| |\
| | |
| | |
| | | |
Merge-request: !2192
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !2191
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
2a5f5c0e31 option: respect existing normal variable
12e6f83319 Option: Add a test that verifies interaction with normal variables
5bb3d40a28 cmOption: Remove VTK 4.0 workarounds
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2155
|
| | | | |
| | | | |
| | | | |
| | | | | |
Add policy CMP0077 to change this behavior in a compatible way.
|
|\ \ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
89e3e62e13 Help: fix add_compile_definitions() documentation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2192
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes: #18147
|
|\ \ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
0d7114987c Revert "target_link_libraries: Allow use with targets in other directories"
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2191
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Revert commit v3.12.0-rc1~82^2 (target_link_libraries: Allow use with
targets in other directories, 2018-05-11). The RHS target scoping and
visibility rules are not clear and will need further investigation
before the feature can be added.
Issue: #17943
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
5dbee9d2d0 math: Add options to calculate and format output as hexadecimal
8661e7052c math: Diagnose divide-by-zero
7c4c13ffef math: Reject unexpected expression input explicitly
5b0f73a15a math: Use 64-bit integer type for computation
963b8d9f6c math: Add RunCMake.math test to prepare for error cases
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2056
|
| | | | | |
|
|\ \ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
19f338109d Help: Clarify ...<max> behavior for policy-related commands
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2180
|
| | |/ /
| |/| |
| | | | |
Affects cmake_minimum_required() and cmake_policy(VERSION)
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
e89ad0f94e install: Allow installing targets created in another directory
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2152
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, `install(TARGETS)` would only accept targets created in the same
directory scope. Relax this restriction by searching the global scope when
determining whether or not a target exists.
Fixes: #14444
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
316815e1f4 target_sources: Interpret relative paths as relative to the calling directory
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2128
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the command considered non-absolute source file paths relative to
the associated target on the LHS. This causes problems in incremental builds
where files are added from subdirectories and forces users to workaround by
manually converting to absolute paths. Change this to enable more intuitive
usage by projects.
Fixes #17981
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
49a51a61d7 list: Add options to control the SORT comparison operation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2065
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
66ea1a3795 LINK_OPTIONS: Add support of "LINKER:" prefix
c1f5a44b28 LINK_OPTIONS: Add new family of properties
8e28d2630a Makefile generator: link flags management refactoring
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Alex Turbov <i.zaufi@gmail.com>
Merge-request: !2033
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This family enable to manage link flags
Three new properties:
* directory property: LINK_OPTIONS
* target properties: LINK_OPTIONS and INTERFACE_LINK_OPTIONS
Two new commands
* add_link_options(): to populate directory property
* target_link_options(): to populate target properties
Fixes: #16543
|
|/
|
|
| |
Fixes: #15785
|
|
|
|
| |
Found via `codespell` and `grep`
|
|
|
|
|
|
|
|
| |
Previously the command did not allow naming targets on the LHS that
were not created in the calling directory. Lift this restriction to
enable more flexible use by projects.
Fixes: #17943
|
|
|
|
|
|
|
|
| |
This change reworks ctest_start() so that simply calling
ctest_start(APPEND) will read all the information from the TAG file.
On top of that, it relaxes the argument parsing for ctest_start() to
allow greater flexibility in the argument ordering, and the documentation
for ctest_start() has been cleaned up.
|
|
|
|
|
|
| |
Add a synopsis section at the top summarizing all signatures.
Issue: #17948
|
|
|
|
|
|
|
|
|
| |
Summarize the command signatures in one block at the top of the
documentation as is typical in Unix command-line tool manuals.
Make the mode keywords links to the corresponding full signature
and documentation.
Issue: #17948
|
|
|
|
|
| |
The LENGTH, GET, JOIN, and SUBLIST operations all read the list without
modifying it. Name their section appropriately.
|
|
|
|
| |
Prepare for the addition of section headers for grouping commands.
|
|\
| |
| |
| |
| |
| |
| |
| | |
af1c48871c CPack: Use project version as default for `CPACK_PACKAGE_VERSION`
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Harry Mallon <hjmallon@gmail.com>
Merge-request: !2020
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Introduce `CMAKE_PROJECT_VERSION` and the corresponsing components:
`CMAKE_PROJECT_VERSION_MAJOR`, `CMAKE_PROJECT_VERSION_MINOR`,
`CMAKE_PROJECT_VERSION_PATCH` and `CMAKE_PROJECT_VERSION_TWEAK`.
* `CPack` module use `CMAKE_PROJECT_VERSION_MAJOR`,
`CMAKE_PROJECT_VERSION_MINOR` and `CMAKE_PROJECT_VERSION_PATCH`
to initialize corresponsing CPack variables.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
7e8046e20b Help: add release notes for NAMELINK_COMPONENT
c02eeb0853 Help: clarify "undefined behavior" in install(EXPORT) command
edcb545a24 install: add test for new NAMELINK_COMPONENT parameter
0212d7c762 install: add NAMELINK_COMPONENT argument
cbb609072f Help: clean up install(TARGETS) documentation
b81280ba1f Help: add list of command signatures to top of INSTALL page
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Alex Turbov <i.zaufi@gmail.com>
Merge-request: !1982
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The "undefined behavior" that the install(EXPORT) command warned about
was simply the possibility of build errors (or other errors) if the
referenced targets aren't installed. As long as the referenced targets
are installed, this won't be an issue.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For shared libraries, this allows you to specify separate components
for the shared library and for the namelink.
Suggested in https://cmake.org/pipermail/cmake-developers/2014-December/024032.html.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The documentation for install(TARGETS) has been rearranged so that
the options are presented as a list, for better readability and
maintenance.
|
| |/ |
|