| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add option `DEPENDS_EXPLICIT_ONLY` to `add_custom_command` to indicate
that implicit dependencies coming from users of the output are not
needed, and only consider dependencies explicitly specified in the
custom command.
Fixes: #17097
|
|/ / |
|
|\ \
| |/
| |
| |
| |
| |
| | |
20e727a408 Help: Clarify that <PackageName>_ROOT variable names are case-preserved
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8182
|
| |
| |
| |
| |
| | |
The name comes from the case-preserved first argument to
`find_package`.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
e7f7bff4f5 Kate: improve the way the VCS-specific files are searched
96389b4cd3 Kate: add support for hg and fossil
4c32623f5f Help: fix typo in docs for set_property()
9a7612d2d0 Kate: make it possible to force a mode for the "files" entry
8a7aa2642b Help: add documentation for Kate-related variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8154
|
| | |
|
|/
|
|
|
|
|
| |
These parameters are so important that it's worthwhile to be more
explicit about their interaction.
Fixes: #24392
|
|
|
|
| |
Issue: #24372
|
|
|
|
| |
Fixes #24351
|
|\
| |
| |
| |
| |
| |
| | |
a1dc38a567 Help: Document behavior of if(EXISTS,IS_DIRECTORY) for empty paths
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8109
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Document and add explicit tests for empty string input:
`if(EXISTS "")` and `if(IS_DIRECTORY "")` are always false.
This avoids need for users to do extra checks due to
CMake non-short-circuit logic as below:
if("${p}")
if(EXISTS "${p}")
|
|/ |
|
|
|
|
|
|
|
| |
Provide a replacement for `file(APPEND .../CMake{Output,Error}.log)`
that records messages in the configure log.
Issue: #23200
|
| |
|
| |
|
|
|
|
| |
Issue: #23200
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
dfab263825 Help: Clarify and update SYSTEM-related docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8027
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
22d36aa0f8 Help: string(JSON): avoid duplicate labels
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8028
|
| |/ |
|
|\ \
| |/
| |
| |
| |
| |
| | |
2ee845c0a5 Help: Add version information for SYSTEM option of add_subdirectory
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8025
|
| | |
|
| |
| |
| |
| | |
Fixes: #24186
|
| |
| |
| |
| | |
This is a common use case, so add an example demonstrating it.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The "In makefile terms" explanation is left from very early days of
CMake to help developers migrating from hand-written makefiles.
These days it is often misinterpreted, particularly in the context
of multiple `add_custom_command` calls, to mean that we generate a
single Makefile containing rules for all custom commands. This
leads to an incorrect mental model of the expressed build system.
The actual generated build system may spread the rules across multiple
targets that do not see the each other's file-level rules, which makes
target-level dependencies important too.
|
|\ \
| |/
| |
| |
| |
| |
| | |
b15b9cf286 Help: Clarify SYSTEM property default for imported targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7990
|
| |
| |
| |
| |
| |
| | |
The `SYSTEM` directory property does not affect imported targets.
Fixes: #24219
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
1046a61cfd Help: clean up and clarify block() and return()
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7872
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f03a1833e2 Help: Update compiler-specific add_compile_options() example and prose
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7959
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Avoid hard-coding a warning-as-error flag now that CMake offers a
first class abstraction for that.
Also mention some relevant generator expressions which can be used
to provide even more specific targeting with language-specific flags.
Fixes: #24200
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
26d813092b add_custom_{command,target}: add genex support for COMMENT
60a5a39022 cmCustomCommandGenerator: refactor GetComment to return std::string
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7887
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Evaluate and expand generator expressions in the `COMMENT` argument of
the `add_custom_command()` and `add_custom_target()` commands.
This allows to include generator expressions, e.g. a targets location
$<TARGET_...> or the current configuration $<CONFIG>, in the build-time
messages.
Fixes #22507
|
|/ / /
| | |
| | |
| | |
| | | |
At least the top-reference links. Internal `:ref:` usages have been left
intact.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On Windows, a file may be inaccessible for a short time after it is
created. This occurs for various reasons, including indexing, antivirus
tools, and NTFS's asynchronous semantics. Add an `INPUT_MAY_BE_RECENT`
option to tell CMake that the input file may have been recently created
so that we can retry a few times to read it.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows the Zstd compression-level to be set between 0-19. I've
adjusted some of the tests, and error messages to indicates the selected
algorithm, and min/max of its compression-level.
Fixes: #24160
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The top-level project() call will now issue an AUTHOR_WARNING if it
wasn't called after cmake_minimum_required().
Fixes: #24071
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
d4d1f85297 Help: Move a note about arguments and genexes into include file
968224484f Help: Drop unused `PROPERTY_GENEX` replace from `prop_tgt/INTERFACE_*` files
65457e4fae Help: Add _See Also_ sections to related CMake commands
c86ec79d07 Help: Use direct refs to genexes instead of ``$<GENEX-NAME>``
8c6274326d Help: Use CMake highlighting for command synopsis
c356a94512 Help: Use monospaced font for a genex name in a section title
f98c8707f4 Help: Use `code-block:: cmake` instead of `::` for sub-commands descriptions
2ba351ca4f Help: ``CMake`` → CMake
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7873
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Most of CMake commands use it. Fix a few of them to do the same.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Most of CMake commands use syntax highlighting when describe
sub-commands syntax. Fix a few of them to be like others...
|
| | | |
| | | |
| | | |
| | | | |
To make it similar to other commands.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
When mention execitable names use Sphinx semantic role `:program`
instead of ``executable`` or **executable**.
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
1046a61cfd Help: clean up and clarify block() and return()
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7872
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | /
| | |/
| |/|
| | |
| | | |
7e1a4567fb Help: Make VALIDATOR wording clearer and more precise
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7874
|