summaryrefslogtreecommitdiff
path: root/Help/command
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'doc-install-typo'Craig Scott2022-04-041-1/+1
|\ | | | | | | | | | | | | 7431759ebc Help: Fix typo in install command documentation Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7140
| * Help: Fix typo in install command documentationEugene Shalygin2022-04-041-1/+1
| |
* | Merge topic 'help-json-length-empty-index'Brad King2022-03-311-1/+1
|\ \ | |/ | | | | | | | | | | 2f0a3d43e1 Help: Fix string(JSON ... LENGTH ...) signature Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7126
| * Help: Fix string(JSON ... LENGTH ...) signatureTobias Nießen2022-03-301-1/+1
| | | | | | | | | | 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.
* | cmake -E tar: Add --touch optionKasper Laudrup2022-03-231-1/+6
| | | | | | | | | | | | | | | | 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
* | Merge topic 'initialize-property-name'Brad King2022-03-231-2/+4
|\ \ | |/ | | | | | | | | | | 26caa97057 define_property(): Change constraints of INITIALIZE_FROM_VARIABLE Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7103
| * define_property(): Change constraints of INITIALIZE_FROM_VARIABLEKyle Edwards2022-03-231-2/+4
| | | | | | | | | | | | | | 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
| * Merge topic 'cleanup-define_property' into release-3.23Brad King2022-03-221-11/+15
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | \ Merge topic 'cleanup-define_property'Brad King2022-03-221-11/+15
|\ \ \ | | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | Help: Update the main purpose of define_property()Craig Scott2022-03-191-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | Help: Clean up INITIALIZE_FROM_VARIABLE define_property() optionCraig Scott2022-03-191-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | | Merge topic 'doc-test-property-genex'Brad King2022-03-223-8/+26
|\ \ \ | | |/ | |/| | | | | | | | | | | | | 78e0204e81 Help: Clarify when add_test and test properties support generator expressions Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7101
| * | Help: Clarify when add_test and test properties support generator expressionsBrad King2022-03-213-8/+26
| |/ | | | | | | Issue: #23329
* | Merge topic 'doc-ignore-prefix-paths'Brad King2022-03-152-0/+10
|\ \ | |/ | | | | | | | | | | 5cb0a730c9 Help: Clarify behavior of search ignore-related variables Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7056
| * Help: Clarify behavior of search ignore-related variablesCraig Scott2022-03-132-0/+10
| | | | | | | | | | | | | | | | | | | | | | 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
* | find_package: Add support for default GLOBAL imported targetsJohn Parent2022-03-101-1/+7
| | | | | | | | | | | | | | | | | | 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.
* | Merge topic 'ctest_truncate'Brad King2022-03-091-2/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | ctest: add option for output truncationFrank Winklmeier2022-03-081-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge topic 'doc-file-sets'Brad King2022-03-092-76/+80
|\ \ \ | | |/ | |/| | | | | | | | | | | | | | | | 4286b72240 Help: Update install() docs to better reflect preference for file sets ab1b573f41 Help: Reorganise FILE_SETS and related properties Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7031
| * | Help: Update install() docs to better reflect preference for file setsCraig Scott2022-03-081-21/+39
| | | | | | | | | | | | | | | | | | | | | Previously, headers would typically be installed as bare files or as whole directories. File sets offer a better abstraction and associate headers with a target, installing them as part of the target. Add notes and update examples to draw the reader's attention to the advantages of file sets for headers.
| * | Help: Reorganise FILE_SETS and related propertiesCraig Scott2022-03-051-55/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reduce duplication and make the docs for target_sources() focus on the functionality rather than the properties it modifies. The properties are a lower level quantity, so put the relevant details for them in the property documentation. The target_sources() command only needs to reference the properties, not reproduce the property documentation. Improve the cross-referencing between the HEADER_... property docs. This helps build the mental picture of how they relate to each other.
| * | Merge topic 'file-set-name-requirements' into release-3.23Brad King2022-03-041-1/+2
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | b357d334fc target_sources(): Enforce stricter requirements for FILE_SET name Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Merge-request: !7037
* | \ \ Merge topic 'file-set-name-requirements'Brad King2022-03-041-1/+2
|\ \ \ \ | | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | b357d334fc target_sources(): Enforce stricter requirements for FILE_SET name Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Merge-request: !7037
| * | | target_sources(): Enforce stricter requirements for FILE_SET nameKyle Edwards2022-03-031-1/+2
| | | | | | | | | | | | | | | | Fixes: #23286
* | | | Merge topic 'file-set-multiple-names'Brad King2022-03-041-2/+3
|\ \ \ \ | | |/ / | |/| | | | | | | | | | | | | | | | | | 8c23ecbd93 target_sources(): Process multiple FILE_SET arguments per block Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7040
| * | | target_sources(): Process multiple FILE_SET arguments per blockKyle Edwards2022-03-031-2/+3
| |/ / | | | | | | | | | Fixes: #23287
* | | Merge topic 'file-set-no-custom-targets'Brad King2022-03-021-1/+2
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | ad41c9cd11 target_sources(): Prohibit FILE_SET on custom targets Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Merge-request: !7027
| * | target_sources(): Prohibit FILE_SET on custom targetsKyle Edwards2022-02-281-1/+2
| | | | | | | | | | | | Fixes: #23262
* | | file(DOWNLOAD): Add options to download a rangem.klimenko2022-02-151-0/+12
|/ /
* | Help: Organize and clarify export() command documentationBrad King2022-02-141-43/+88
|/ | | | | | | | | Add section headers for each signature, and a synopsis linking to them. Re-order sections to introduce the main `export(TARGETS)` functionality before mentioning the `export(EXPORT)` shorthand, which may be confused with `install(EXPORT)`. Fixes: #23221
* Help: Clarify precedence of AND and OR in 'if' conditionsBrad King2022-02-091-8/+15
| | | | | | | | | | | | The wording update in commit b74819e4fe (Help: Format 'if' command documentation, 2013-12-18, v3.0.0-rc1~227^2~1) incorrectly implied that `AND` has higher precedence than `OR`. Although this is common in many languages, it has never been true in CMake's implementation. Revise the wording to clarify the precedence. Add a test case demonstrating the order. Fixes: #23207
* Help: Clarify documentation on SYSTEM include directoriesBrad King2022-02-031-6/+9
| | | | | | | | Mention that system include directories are searched after normal include directories. Document that `IMPORTED_NO_SYSTEM` and `NO_SYSTEM_FROM_IMPORTED` do not affect `INTERFACE_SYSTEM_INCLUDE_DIRECTORIES`.
* Merge topic 'help-try-compile-result-var'Brad King2022-02-012-13/+0
|\ | | | | | | | | | | | | 34d263270e Help: Drop incorrect versionadded for try_compile result variable Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6923
| * Help: Drop incorrect versionadded for try_compile result variablefriendlyanon2022-01-312-13/+0
| | | | | | | | | | | | | | | | | | | | | | | | In commit c705279bae (Help: Add `.. versionadded` directives to commands documentation, 2020-11-08, v3.20.0-rc1~508^2) we accidentally added ``versionadded`` markup suggesting that the first argument to `try_compile` was fixed as `RESULT_VAR` prior to CMake 3.14. This was probably due to misinterpreting the change from commit 7975edeac5 (Help: User-provided variable names for try_* commands, 2019-02-24, v3.14.0-rc3~16^2~3). The result variable has never been fixed. Drop the incorrect markup.
| * Help: cmake_path: fix erroneous example for IS_PREFIXMarc Chevrier2021-06-121-3/+4
| |
* | Help: Clarify relative path handling for target_include_directories()Craig Scott2022-01-311-8/+17
| | | | | | Fixes: #22853
* | string(TIMESTAMP): add %f specifier for microsecondsPeter Würth2022-01-281-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The %f specified extends the string(TIMESTAMP) and file(TIMESTAMP) commands to output the timestamp with a microsecond resolution. This convention is offered by python's datetime module. Before, the precision was limited to seconds. The implementation is done by extending existing cmTimestamp methods with a `microseconds` parameter. This parameter is optional in order to be backwards compatible. The timestamps are now received in a cross-platform manner using libuv, since the standard C functions like time() don't allow for sub-second precision. This requires libuv 1.28 or higher. We already require higher than that on Windows, so update the required version for other platforms. Implements: #19335
* | Help: Note the version in which define_property() arguments became optionalKyle Edwards2022-01-211-0/+4
| |
* | define_property(): Add INITIALIZE_FROM_VARIABLE argumentKyle Edwards2022-01-201-1/+7
| | | | | | | | Fixes: #20698
* | Merge topic 'define-property-optional-args'Brad King2022-01-191-2/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | edb5059216 define_property(): Make BRIEF_DOCS and FULL_DOCS optional 7d26baff46 cmDefinePropertyCommand: Refactor to use cmArgumentParser Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Merge-request: !6875
| * | define_property(): Make BRIEF_DOCS and FULL_DOCS optionalKyle Edwards2022-01-181-2/+2
| | | | | | | | | | | | Issue: #20698
* | | Depfile parsing: enhance compatibility with GNU MakeMarc Chevrier2022-01-161-4/+3
|/ /
* | Help: add_custom_command: describes depfile formatMarc Chevrier2022-01-111-3/+42
| |
* | Help: Non-zero floating point numbers are true in if() expressionsCraig Scott2022-01-041-1/+2
| | | | | | Fixes: #22991
* | Help: mention non-existent case for list(PREPEND)Adriaan de Groot2021-12-211-1/+3
| |
* | Help: clarify range for list(INSERT), mention nonexistent / empty caseAdriaan de Groot2021-12-211-1/+6
| |
* | Help: clarify description of list(INSERT)Adriaan de Groot2021-12-211-1/+1
| | | | | | | | Since the argument is called 'index', use that in the description.
* | Help: clarify that list(APPEND) on a non-existent list creates itAdriaan de Groot2021-12-211-1/+3
| | | | | | | | | | | | | | | | This is hinted-at in the introduction, which mentions creating a new variable value in the current scope, but let's make it explicit. Fixes: #22910
* | Help: Clarify behavior of if(DEFINED) for cache and non-cache variablesCraig Scott2021-12-201-1/+10
| | | | | | Fixes: #23023
* | Merge topic 'doc-if-basic-expressions'Brad King2021-12-011-4/+15
|\ \ | | | | | | | | | | | | | | | | | | | | | 294581a443 Help: Be more explicit about the behavior of if(<string>) 3a9695557d Help: Explicitly state that if(ENV{some_var}) is always false Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6768
View Lorry Controller Status