| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Help: Add _See Also_ sections to related CMake commands | Alex Turbov | 2022-11-09 | 1 | -4/+9 |
| | | |||||
| * | Help: Add `.. versionadded` directives to commands documentation | Nikita Nemkin | 2020-11-09 | 1 | -0/+3 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 | ||||
| * | Help: Apply syntax highlighting to project commands | Joachim Wuttke (o) | 2018-10-25 | 1 | -2/+2 |
| | | | | | | | * Replace most "::" by ".. code-block:: cmake" * Header sentence in imperative voice, detailed command description in present tense. | ||||
| * | Help: Explicitly mention lack of 'install' support in add_dependencies | Brad King | 2015-06-01 | 1 | -1/+2 |
| | | | | | | | CMake-generated targets are not supported by add_dependencies. State this explicitly and use 'install' as an example since this may be commonly attempted. | ||||
| * | Allow add_dependencies() on INTERFACE libraries (#15414) | Brad King | 2015-03-27 | 1 | -2/+2 |
| | | | | | | | | | | | Revert commit v3.0.0-rc1~175^2~20 (add_dependencies: Disallow use with INTERFACE_LIBRARY, 2013-12-25). Teach our dependency analysis to transitively follow INTERFACE target utility dependencies as was done or IMPORTED targets in commit v2.8.6~127^2~1 (Allow add_dependencies() on imported targets, 2010-11-19). Extend the InterfaceLibrary test with a case to cover header generation for a header-only INTERFACE library via a custom target. | ||||
| * | Help: Format add_dependencies documentation | Brad King | 2015-03-27 | 1 | -9/+12 |
| | | | | | Add reStructuredText markup. | ||||
| * | Convert builtin help to reStructuredText source files | Kitware Robot | 2013-10-15 | 1 | -0/+19 |
| Run the convert-help.bash script to convert documentation: ./convert-help.bash "/path/to/CMake-build/bin" Then remove it. | |||||
 |
index : CMake.git | |
| CMake is a cross-platform, open-source build system generator. |
| summaryrefslogtreecommitdiffstats |