Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Help: Add Sphinx 'versionadded' directives to each top-level document | Kitware Robot | 2020-07-06 | 1 | -0/+2 |
| | | | | | | | Run the `Utilities/Sphinx/update_versions.py` script to add initial markup to every top-level document and find module. Issue: #19715 | ||||
* | Help: Fix minor typo in docs for CMAKE_PROJECT_DESCRIPTION | Craig Scott | 2018-03-16 | 1 | -1/+1 |
| | |||||
* | Help: Fix incorrect CMAKE_PROJECT_xxx docs | Craig Scott | 2018-03-13 | 1 | -3/+31 |
| | | | | | | | | | 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 | ||||
* | project: Add `DESCRIPTION` parameter | Alex Turbov | 2017-04-11 | 1 | -0/+7 |
It is quite often the project description has used in a real world software. Examples include: * part of a help screen of the application * builtin resources (`*.rc` files, data for "About" dialog of a GUI app, & etc) * most generators for CPack can use it * it could be used by documentary software (Doxygen, Sphinx) which is usually integrated to CMake based projects via `add_custom_target()` Now `project()` call learned an optional `DESCRIPTION` parameter with a short string describing a project. Being specified, it would set the `PROJECT_DESCRIPTION` variable which could be used in `configure_file()` or whatever user wants. Also `PROJECT_DESCRIPTION` is a default value for `CPACK_PACKAGE_DESCRIPTION_SUMMARY`. |