| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
c0e05671d3 Help/get_filename_component: clarify NAME_W[L]E summaries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5489
|
| |
| |
| |
| |
| |
| | |
There was an ambiguity in the wording with the meaning of "or" typically
meaning exclusive-or in prose. Instead, ensure that the easiest parsing
is clear that the directory part is always removed.
|
| |
| |
| |
| |
| |
| |
| | |
Defer adding this command until post-3.19 development so that it
has more time to mature before being included in a release.
Issue: #21385
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
49fce3373b Help: Clarify string(JSON) error handling
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5427
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change ony concerns directives that appear in the document body.
The guidelines for inserting version directives:
* Baseline version is CMake 3.0, i.e. directives start at 3.1.
* Always use `.. versionadded::` directive, avoid ad-hoc version
references. Exception: policy pages.
* For new command signatures, put `versionadded` on a separate line
after the signature.
* For a group of new signatures in a new document section,
a single version note at the beginning of the section is sufficient.
* For new options, put `versionadded` on a separate line before
option description.
* If all the option descriptions in the list are short one-liners,
it's fine to put `versionadded` on the same line as the description.
* If multiple option descriptions in close proximity would have
the same ..versionadded directive, consider adding a single
directive after the list, mentioning all added options.
* For compact value lists and sub-option lists, put a single
`versionadded` directive after the list mentioning all additions.
* When a change is described in a single paragraph, put
`versionadded` into that paragraph.
* When only part of the paragraph has changed, separate the changed
part if it doesn't break the flow. Otherwise, write a follow-up
clarification paragraph and apply version directive to that.
* When multiple version directives are close by, order earlier
additions before later additions.
* Indent related lists and code blocks to include them in the scope
of `versionadded` directive.
Issue: #19715
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
49fce3373b Help: Clarify string(JSON) error handling
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5427
|
| | |
| | |
| | |
| | | |
Closes: #21355
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
ec5951e078 cmake_path: Enhance documentation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5425
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
03ad0e61c1 configure_file: Add option for user defined permissions
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5320
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
User defined permissions and options to copy permissions are
implemented.
Fixes: #20866
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
1a3d125de8 target_sources: Support custom targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5421
|
| |/ /
| | |
| | |
| | | |
Fixes: #21034
|
|\ \ \
| |/ /
|/| /
| |/
| |
| |
| | |
95c14579f2 Help: Cleanup typos and grammar for the 3.19 release
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5419
|
| | |
|
| | |
|
|/
|
|
| |
Fixes: #21267
|
|
|
|
| |
Fixes: #19930
|
|
|
|
| |
Fixes: #19575
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
5b3356263c CMakePackageConfigHelpers: Add version range support
6bfc442fde FPHSA: add support of version range
d7df81067b find_package: Add support of version range
09095dbcd2 cmFindPackageCommand: Refactoring
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Michael Hirsch, Ph.D. <michael@scivision.dev>
Merge-request: !5226
|
| |
| |
| |
| | |
This enhancement is the first step for solving issue #21107
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
d832c1cc7d separate_arguments: add option PROGRAM
f4c21d4953 separate_arguments: refactoring
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5253
|
| |/
| |
| |
| | |
Fixes: #21217
|
|/
|
|
|
|
|
| |
Index directories by their binary directory path in addition to their
source directory path.
Fixes: #19262
|
|\
| |
| |
| |
| |
| |
| |
| | |
82c9508313 cmake_path: enhancements
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !5245
|
| |
| |
| |
| |
| | |
* Fix error on parsing "c:a" (root-name without root-directory)
* Enrich documentation
|
|/
|
|
| |
Fixes: #21125
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
8eab76eb84 string(JSON): Adds JSON parsing support to the string command
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Acked-by: Cristian Adam <cristian.adam@gmail.com>
Acked-by: Michael Hirsch, Ph.D. <michael@scivision.dev>
Merge-request: !5159
|
| |
| |
| |
| |
| |
| |
| | |
Adds a set of sub commands to the string command for parsing JSON, the
JSON commands are: GET, TYPE, MEMBER, LENGTH, REMOVE, SET, and EQUAL.
Closes: #19501
|
|/ |
|
| |
|
|
|
|
|
|
| |
Fix a typo accidentally added by commit eb583b0a66 (cmake_path command:
path management, 2020-07-23). Remove a stray `]` character that breaks
the pygments lexer.
|
|
|
|
| |
Fixes: #19568, #20922
|
|\
| |
| |
| |
| |
| |
| |
| | |
f14b390198 GenEx: Remove unneeded dependencies from target info queries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Raul Tambre <raul@tambre.ee>
Merge-request: !5127
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Only generate a graph dependency between a custom command and
a target when the custom command queries for the file path
of an artifact of the target.
This makes generator expressions such as `TARGET_FILE_DIR`
behave the same way as `TARGET_PROPERTY` which never generated
a graph dependency.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
7de60beddf file: Add CHMOD and CHMOD_RECURSE subcommands
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Marc Chevrier <marc.chevrier@gmail.com>
Merge-request: !5122
|
| |/
| |
| |
| |
| |
| | |
Fixes: #21057
Signed-off-by: Sibi Siddharthan <sibisiddharthan.github@gmail.com>
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
5ece12b7e4 gitlab-ci: add ISPC to the Fedora CI image
8976817d6d ISPC: Update help documentation to include ISPC
2368f46ba4 ISPC: Support building with the MSVC toolchain
e783bf8aa6 ISPC: Support ISPC header generation byproducts and parallel builds
34cc6acc81 Add ISPC compiler support to CMake
419d70d490 Refactor some swift only logic to be re-used by other languages
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5065
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Adds TARGET argument to file(GENERATE) to make resolving generator expressions
requiring a target possible.
Implements #21101, fixes #21074.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Restore the change from commit f84af8e270 (add_test: Allow special
characters in test name, 2020-05-16, v3.18.0-rc1~142^2) that had to be
reverted by commit f84af8e270 (add_test: Allow special characters in
test name, 2020-05-16, v3.18.0-rc1~142^2) for compatibility.
Add policy CMP0110 to make the change in a compatible way.
Also, support even more characters than before by generating the
test scripts using bracket arguments around the test names.
Fixes: #19391
Signed-off-by: Deniz Bahadir <dbahadir@benocs.com>
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
bafa9fe887 fileapi: Add INTERFACE libraries with SOURCES to codemodel-v2
4391913133 Add INTERFACE libraries to generated buildsystem if they have SOURCES
afb998704e Remove filtering of allowed INTERFACE library properties
e7edba2baf Makefiles: Use IsInBuildSystem in global generator target type checks
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5078
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
INTERFACE libraries were created with the intention of collecting usage
requirements for use by other targets via `target_link_libraries`.
Therefore they were not allowed to have SOURCES and were not included in
the generated buildsystem. In practice, this has become limiting:
* Header-only libraries do have sources, they just do not compile.
Developers should be able to edit those sources (the header files)
in their IDE.
* Header-only libraries may need to generate some of their header
files via custom commands.
Some projects work around these limitations by pairing each interface
library with an `add_custom_target` that makes the header files and
custom commands appear in the generated buildsystem and in IDEs.
Lift such limitations by allowing INTERFACE libraries to have SOURCES.
For those with sources, add a corresponding build target to the
generated buildsystem.
Fixes: #19145
|
|/
|
|
| |
Fixes: #21053
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ee5b58f491 Help: State in add_library that INTERFACE libraries have no build targets
99b1e85f07 Help: Consolidate add_library documentation on IMPORTED libraries
716e76be3e Help: Re-order add_library sections
1b0adeea81 Help: Clarify target_sources PRIVATE/PUBLIC/INTERFACE scopes
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5086
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Move documentation on IMPORTED INTERFACE libraries to the main section
on Imported Libraries. Revise the section to clarify the different
kinds of imported libraries that can be created and what properties they
need.
Issue: #18975
|
| |
| |
| |
| |
| | |
Put all the sections that create in-project targets first,
and move Imported Libraries and Alias Libraries at the end.
|
| | |
|