| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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.
|
| |/ |
|
|/
|
|
| |
Fixes: #17949
|
|\
| |
| |
| |
| |
| |
| | |
20d90a9482 Help: Some spelling corrections for commands.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1994
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a4f71b4ba8 Help: Document existence of cmake_install.cmake
fcf64866da Help: move DESTDIR into a separate page
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1979
|
| |/
| |
| |
| |
| |
| | |
This file, which is currently undocumented, is useful for external
packaging programs that wish to install only a single component at a
time. This change adds documentation for the file.
|
|/
|
|
|
|
|
| |
This command manages preprocessor definitions at directory level and
supports generator expressions.
Fixes: #15374
|
| |
|
|
|
|
| |
Issue: #17823
|
|
|
|
|
|
|
|
|
|
| |
`install(EXPORT_ANDROID_MK)` is its own mode, not an option to the
normal `install(EXPORT)` mode.
While at it, also fix the prose in our documented example to match
the code.
Fixes: #17891
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
6c4f8b4596 Adjust help documentation for file(GLOB), add topic notes
20612978c8 Add tests for `file(GLOB)` CONFIGURE_DEPENDS flag
3f4b81f540 Add glob verify support to XCode, VS, Ninja, and Makefile generators
ca0befc2e1 Add `CONFIGURE_DEPENDS` flag support to cmFileCommand::HandleGlobCommand
599c93e22d Add cmGlobVerificationManager class, integrate with cmake and cmState
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1767
|
| | |
|
|/
|
|
| |
This generator has been deprecated since CMake 3.9. Remove it.
|
|\
| |
| |
| |
| |
| |
| | |
4eb5d851d5 Help: Add 'lib32|libx32|lib64' paths to find_package prefixes
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1878
|
| |
| |
| |
| |
| | |
Document the conditions when 'lib32|libx32|lib64' variants will be added to the
list of possible installation prefixes.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
768225837d list: Add SUBLIST sub-command
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1874
|
| |/
| |
| |
| | |
Issue: #17823
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
45408b5ea1 cmake_minimum_required: Optionally set policies with version range
6a41aa2abd cmPolicies: Split parsing and impl of ApplyPolicyVersion
1d00ed7cf7 cmPolicies: Drop unnecessary check from ApplyPolicyVersion
0df559832b cmPolicies: Pass policy version as std::string
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1864
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Teach `cmake_minimum_required` and `cmake_policy(VERSION)` to support a
version range of the form `<min>[...<max>]`. Define this to mean that
version `<min>` is required, but known policies up to those introduced
by `<max>` will be set to `NEW`. This will allow projects to easily
specify a range of versions for which they have been updated.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
ff6234509e Help: Clarify behavior of INHERITED properties
9cc97ab4dc Tests: Add tests for INHERITED property chaining
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1879
|
| | | |
| | | |
| | | | |
Fixes: #17839
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
3af1daa186 Help: Document target_compile_definitions handling of -D
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1873
|
| |/ /
| | |
| | |
| | |
| | | |
Add an example of using the `target_compile_definitions` command and a
note about usage of ``-D`` in items.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
a58158727b list(): add `JOIN` sub-command
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1846
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
89ee7ce3ea Help: Reference set_property from set_target_properties
c27e3e0f2b Help: Clarify that set_target_properties supports multiple targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1866
|
| | | |
|
| | |
| | |
| | |
| | | |
Reported-by: Alan W. Irwin <irwin@beluga.phys.uvic.ca>
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
eb35d8884b find_package: Use PackageName_ROOT variables as search prefixes
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1858
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This feature was originally added by commit v3.9.0-rc1~71^2~2 (find_*:
Add a new PackageRoot search path group, 2017-05-03) and documented by
commit v3.9.0-rc1~71^2 (find_*: Add docs for PackageRoot search path
group, 2017-05-03). However, we had to disable the feature and remove
the documentation in commit v3.9.1~2^2 (find_*: Disable the PACKAGE_ROOT
search path group for CMake 3.9, 2017-08-08) due to breaking projects
that used `PackageName_ROOT` variables themselves.
Add policy `CMP0074` to restore the `PackageName_ROOT` variable behavior
in a compatible way. Also revise the stack of root paths to store the
paths themselves rather than the package names. This way the policy can
be considered at the `find_package` call site instead of individual
`find_` calls inside a find module.
Co-Author: Chuck Atkins <chuck.atkins@kitware.com>
Issue: #17144
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
81226c73a4 Help: refresh list() command documentation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1860
|
| |/
| |
| |
| |
| | |
Reformat `list` command documentation be consistent with the `string`
command.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
73f9b2974c project: Add HOMEPAGE_URL named parameter
fd28c382b4 project: Add <PROJECT-NAME>_DESCRIPTION
9b57cb62ea Help: Fix minor typo in docs for CMAKE_PROJECT_DESCRIPTION
c89993d529 Tests: Avoid enabling languages unnecessarily in RunCMake.project
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1816
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This sets variables like PROJECT_HOMEPAGE_URL, which can be
used as default values for various things (packaging modules,
doxygen defaults, etc.). Some packaging modules have been
updated to do this as part of this commit.
Co-Author: Craig Scott <craig.scott@crascit.com>
|
| |
| |
| |
| | |
For consistency with the VERSION keyword, also define the
<PROJECT-NAME>_DESCRIPTION variable.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
ce0b983216 target_compile_options: Add syntax to specify shell strings
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1841
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Options specified via `COMPILE_OPTIONS` and `INTERFACE_COMPILE_OPTIONS`
are deduplicated, but individual options can legitimately be duplicated
when grouped with other options, e.g.
-D A -D B
After deduplication that becomes `-D A B`. Therefore we need a way to
treat groups of options as units during deduplication. A simple approach
is to specify each group as one option, e.g.
"-D A" "-D B"
However, that conflicts with options that legitimately have spaces. To
break this ambiguity, add a `SHELL:` prefix syntax to specify that an
option should be parsed like shell command line arguments after
deduplication, e.g.
"SHELL:-D A" "SHELL:-D B"
These will survive deduplication intact, and then be parsed to produce
`-D A -D B` on the final command line.
Fixes: #15826
|
|/
|
|
|
|
|
|
|
| |
The docs for CMAKE_PROJECT_NAME and CMAKE_PROJECT_DESCRIPTION
were erroneously documenting the behavior of PROJECT_NAME and
PROJECT_DESCRIPTION respectively. Fix these and update the
project() docs to also mention CMAKE_PROJECT_NAME and
CMAKE_PROJECT_DESCRIPTION.
Fixes: #17815
|
|
|
|
|
| |
Inspired-by: Deniz Bahadir <dbahadir@benocs.com>
Issue: #14778
|
|\
| |
| |
| |
| |
| |
| | |
ea0ce73a19 install,export: Maybe transform OBJECT libraries to INTERFACE libraries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1811
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Teach the `install` and `export` commands to support installing and
exporting `OBJECT` libraries without their object files. Transform
them to `INTERFACE` libraries in such cases.
For `install(TARGETS)`, activate this when no destination for the object
files is specified. For `export`, activate this only under Xcode with
multiple architectures when we have no well-defined object file
locations to give to clients.
|