summaryrefslogtreecommitdiffstats
path: root/Help
Commit message (Collapse)AuthorAgeFilesLines
* install: Support generator expressions in FILES and PROGRAMS modeBrad King2014-02-212-0/+10
| | | | | | | | Teach the install(FILES) and install(PROGRAMS) commands to evaluate generator expressions in the list of files. Extend the ExportImport test to cover installation cases involving generator expressions.
* Help: Format install() command documentationBrad King2014-02-211-161/+162
| | | | Add inline markup and explicit markup blocks as appropriate.
* Help: Drop development topic notes to prepare releaseBrad King2014-02-192-9/+0
| | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* Help: Rename 3.0 release notes to 3.0.0Brad King2014-02-192-4/+4
| | | | | Bug-fix releases 3.0.x may have their own notes so this will look more consistent.
* Help: Consolidate remaining 3.0 release notesBrad King2014-02-192-5/+3
|
* Merge topic 'doc-usage-requirements'Brad King2014-02-191-0/+6
|\ | | | | | | | | 0c54b775 Help: Document the purpose of usage requirements clearly.
| * Help: Document the purpose of usage requirements clearly.Stephen Kelly2014-02-181-0/+6
| | | | | | | | | | | | | | | | | | | | People will be tempted to put things there for convenience, thereby causing conflicts similar to http://thread.gmane.org/gmane.comp.compilers.clang.devel/35162/focus=35169 where it is conceivable that the LLVM developers could put a flag on a target for convenience, which would cause conflicts for some downstreams.
* | Merge topic 'FindBoost-namespace'Brad King2014-02-191-0/+5
|\ \ | | | | | | | | | | | | 17485e37 FindBoost: Add suport for custom namespaces
| * | FindBoost: Add suport for custom namespacesChuck Atkins2014-02-171-0/+5
| |/ | | | | | | | | | | | | | | | | | | When building boost with an alternate namespace the libraries generated will have a different naming convention. This is often done to ensure no symbol conflicts with external libraries built against a different version of boost. If the namespace used is "myprivateboost::" instead of "boost::" then the libraries built will be named myprivateboost_foo instead of boost_foo. Add an option to specify a custom namespace used to alter the library names that get searched for.
* | Merge topic 'doc-package-registry'Brad King2014-02-192-189/+300
|\ \ | | | | | | | | | | | | | | | bf012e0c Help: Format find_package() command documentation bd6887e4 Help: Document the package registry in cmake-packages.7
| * | Help: Format find_package() command documentationBrad King2014-02-171-189/+171
| | | | | | | | | | | | | | | Add inline markup and explicit markup block syntax as needed. Add cross-references to other documentation as appropriate.
| * | Help: Document the package registry in cmake-packages.7Brad King2014-02-171-0/+129
| |/ | | | | | | | | | | | | | | Port documentation from the CMake Wiki page at: http://www.cmake.org/Wiki/CMake/Tutorials/Package_Registry as of 2014-02-17 into our main documentation.
* | Help: Fix typoStephen Kelly2014-02-171-2/+2
|/ | | | binary_find -> binary_search.
* add_custom_command: Disallow use of SOURCE signatures.Stephen Kelly2014-02-123-0/+22
| | | | Add CMP0050 to control this behavior.
* Add policy CMP0049 to avoid variable expansion in source listsStephen Kelly2014-02-123-0/+29
|
* Help: Add CMake 3.0 Release NotesBrad King2014-02-112-0/+453
| | | | | | | Manually read through version control history since the 2.8.12.2 release and write release notes for important user-facing changes. Co-Author: Stephen Kelly <steveire@gmail.com>
* Merge topic 'doc-policy-version-3.0'Brad King2014-02-1025-29/+29
|\ | | | | | | | | aab11bca Help: Change version 3.0.0 -> 3.0 in policy docs
| * Help: Change version 3.0.0 -> 3.0 in policy docsBrad King2014-02-1025-29/+29
| | | | | | | | | | | | Starting with 3.0 we will use only two components for the feature level, and policies are only ever introduced with a bump to the feature level version.
* | Merge topic 'extend-docs'Brad King2014-02-103-4/+17
|\ \ | | | | | | | | | | | | | | | | | | 0b3e98d9 Help: Don't list debuggable properties in cmake-buildsystem manual. 39d08b92 Help: Add additional hyperlink targets ef17e293 Help: Document SYSTEM treatment of IMPORTED target INTERFACE_INCLUDE_DIRS
| * | Help: Don't list debuggable properties in cmake-buildsystem manual.Stephen Kelly2014-02-101-4/+2
| | |
| * | Help: Add additional hyperlink targetsStephen Kelly2014-02-093-0/+7
| | |
| * | Help: Document SYSTEM treatment of IMPORTED target INTERFACE_INCLUDE_DIRSStephen Kelly2014-02-091-0/+8
| |/ | | | | | | Document how the behavior can be controlled.
* | Merge topic 'release-notes-prep'Brad King2014-02-101-0/+6
|\ \ | | | | | | | | | | | | | | | | | | | | | 4b7f2f52 Help: Add hyperlink targets for argument types in cmake-language(7) 113df227 Remove ChangeLog.manual 79f55909 Remove ChangeLog.txt d25dbc90 Tests/BundleTest: Drop use of ChangeLog.txt
| * | Help: Add hyperlink targets for argument types in cmake-language(7)Brad King2014-02-071-0/+6
| |/ | | | | | | | | Add reStructuredText hyperlink targets for the bracket, quoted, and unquoted argument sections.
* | Help: Fix typo.Stephen Kelly2014-02-071-1/+1
|/ | | | 'to not to' -> 'not to'
* Help: Adjust the QtAutogen properties to the common style.Stephen Kelly2014-02-067-38/+59
| | | | Link to the cmake-qt manual.
* Help: Use ``True`` and ``False`` for IMPORTED values.Stephen Kelly2014-02-061-3/+3
| | | | Only the first letter is capitalized. It is marked up.
* Help: Document relation of properties to the rest of the buildsystem.Stephen Kelly2014-02-0621-144/+203
|
* Help: Mark up the buildsystem commands documentationStephen Kelly2014-02-069-283/+334
| | | | Cross-link to the cmake-buildsystem manual.
* Help: Note that the compatible interface properties must not intersect.Stephen Kelly2014-02-061-0/+4
|
* Help: Specify how to order and modify transitively set property values.Stephen Kelly2014-02-061-1/+21
|
* Help: Add hyperlink targets to some manual sections.Stephen Kelly2014-02-061-0/+9
| | | | | These can be refered to from the command documentation and other relevant locations.
* Help: Use ``inline-literals`` to mark generator expressions.Stephen Kelly2014-02-0613-13/+13
|
* Help: Mark up references to NEW and OLD policy settings properly.Stephen Kelly2014-02-061-4/+4
|
* Help: Add a style guide.Stephen Kelly2014-02-061-2/+167
|
* Help: Fix typosStephen Kelly2014-02-062-2/+2
| | | | | | | | Psuedo -> Pseudo behaviour -> behavior CMake uses American spelling.
* Merge topic 'doc-version-components'Brad King2014-02-055-20/+50
|\ | | | | | | | | 52e7beb6 Help: Expand documentation of CMAKE_VERSION and related variables
| * Help: Expand documentation of CMAKE_VERSION and related variablesBrad King2014-02-055-20/+50
| | | | | | | | | | | | | | | | | | | | | | Describe the meaning of each version component in more detail in the documentation of CMAKE_VERSION. Simplify the per-component version variable documentation by referencing the main variable. Include information about how to compare version strings. Also add an historical note about the version scheme used prior to commit v2.8.2~105^2~4 (New version scheme to support branchy workflow, 2010-04-23).
* | Merge topic 'release-notes'Brad King2014-02-054-0/+47
|\ \ | | | | | | | | | | | | | | | | | | ccc87047 Help: Add documents to collect notes between releases 70309e70 Help: Add documents for release notes 34ea1f15 Utilities/Sphinx: Add option to build 'text' format
| * | Help: Add documents to collect notes between releasesBrad King2014-02-043-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a release/dev.txt file and include it from release/index.rst in development versions. Add a "Changes Since Release" section with a toctree that globs adjacent "dev/*" documents. Add a sample topic document explaining how topic-specific release note documents work. This approach will allow developers to write release notes for their changes as they are made. The release manager may then consolidate and organize the notes for a specific release version.
| * | Help: Add documents for release notesBrad King2014-02-042-0/+18
| |/ | | | | | | | | | | Add a release/index.rst document titled "CMake Release Notes" to hold the toctree for release notes. Add a "Release Notes" section to the top-level html document index to link to the new document.
* | Help: Be clearer about which header files are considered for AUTOMOCAlex Merry2014-02-041-2/+5
|/ | | | | | | | The old documentation stated that "all header files" were considered, which was not true for any sensible definition of "all header files". Only header files with certain names are considered. Document the filename patterns matched for parsing.
* Merge topic 'cmake-qt-manual'Brad King2014-02-032-0/+185
|\ | | | | | | | | | | | | 4271a4ed Help: Add information about INTERFACE_AUTOUIC_OPTIONS. 7935f4de Help: Note that AUTOMOC consumes the defines and includes from targets. 2739a6f9 Help: Move Qt tool invocation information to a generic cmake-qt manual.
| * Help: Add information about INTERFACE_AUTOUIC_OPTIONS.Stephen Kelly2014-02-021-0/+40
| |
| * Help: Note that AUTOMOC consumes the defines and includes from targets.Stephen Kelly2014-02-021-0/+4
| |
| * Help: Move Qt tool invocation information to a generic cmake-qt manual.Stephen Kelly2014-02-022-0/+141
| | | | | | | | | | | | | | | | Add an introduction about the use of different package types, and the ability to use Qt 4 and 5 versions together in a single buildsystem. Add a section about automatic linking of the qtmain.lib library and how to disable it.
* | project: Manage VERSION variablesBrad King2014-01-2914-1/+121
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Teach the project() command to set variables {PROJECT,<PROJECT-NAME>}_VERSION{,_MAJOR,_MINOR,_PATCH,_TWEAK} holding the project version number and its components. Add project() command option "VERSION" to specify the version explicitly, and default to the empty string when it is not given. Since this clears variables when no VERSION is given, this may change behavior for existing projects that set the version variables themselves prior to calling project(). Add policy CMP0048 for compatibility. Suggested-by: Alex Neundorf <neundorf@kde.org>
* | project: Add optional LANGUAGES keywordBrad King2014-01-291-2/+3
| | | | | | | | | | | | | | Teach the project() command to recognize an optional "LANGUAGES" keyword after the project name and prior to the list of languages. Do not allow multiple copies of the keyword. If the keyword is specified and no languages are listed, imply NONE.
* | Help: Format project command and variable documentationBrad King2014-01-298-28/+39
|/ | | | Also add document for CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE variable.
* Help: Note that std::string::clear may not be used.Stephen Kelly2014-01-271-4/+6
| | | | | As found in commit 519c0a5d (Can't use std::string::clear() in cmake., 2012-09-15).
generated by cgit v0.12 at 2025-01-01 09:34:35 (GMT)