summaryrefslogtreecommitdiffstats
path: root/Help/command
Commit message (Collapse)AuthorAgeFilesLines
* Help: Document that file(GENERATE) re-writes only when needed.Stephen Kelly2014-06-051-0/+2
|
* Help: Convert CTest Script variable references to cross-referencesBrad King2014-06-031-3/+5
| | | | | | In the ctest(1) manual and ctest_start() command documentation, convert mentions of CTest Script variables to cross-references so they will be rendered as links.
* Merge topic 'doc-include-dir-props'Brad King2014-06-031-0/+14
|\ | | | | | | | | 907e422b Help: Explain build/install-tree include dirs in more places (#14946)
| * Help: Explain build/install-tree include dirs in more places (#14946)Brad King2014-06-021-0/+14
| | | | | | | | | | | | | | | | | | | | | | Explain how to use $<BUILD_INTERFACE> and $<INSTALL_INTERFACE> directly in the documentation of the target_include_directories command and INTERFACE_INCLUDE_DIRECTORIES target property. Otherwise readers need to notice the link to the cmake-buildsystem(7) manual and find the example in that to understand the need for these expressions. Also fix the explanation in cmake-buildsystem(7) to not claim that relative paths may be used inside a BUILD_INTERFACE expression.
| * Merge branch 'doc-find_package-build-paths' into releaseBrad King2014-03-031-0/+1
| |\
| * \ Merge branch 'add_definitions-no-genex' into releaseBrad King2014-03-031-4/+2
| |\ \
| * \ \ Merge branch 'install-FILES-genex' into releaseBrad King2014-02-241-161/+168
| |\ \ \
* | | | | Help: Use "^^^^" for subsubsection headersBrad King2014-06-021-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is the convention suggested in the Sphinx documentation and is already used in several other places in the CMake documentation. Update a few places where we were using other characters.
* | | | | Merge topic 'feature-extensions-by-default'Brad King2014-06-021-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 60a981ea Features: Enable compiler extensions by default.
| * | | | | Features: Enable compiler extensions by default.Stephen Kelly2014-05-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Compilers enable their extensions by default, and disabling them implicitly can lead to results which are surprising or non-obvious to debug. http://public.kitware.com/pipermail/cmake-developers/2014-May/010575.html http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/10214 https://www.mail-archive.com/cmake-developers@cmake.org/msg10116.html (Compiler feature extensions by default, 29 May 2014)
* | | | | | Merge topic 'doc-ctest-settings'Brad King2014-06-021-0/+6
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2d57a390 Help: Document ctest dashboard client usage 28f73dff Help: Document ctest_start initial checkout command variables
| * | | | | | Help: Document ctest_start initial checkout command variablesBrad King2014-05-301-0/+6
| |/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | Describe the behavior of the ctest_start() command when the CTEST_CHECKOUT_COMMAND or CTEST_CVS_CHECKOUT variable is set.
* | | | | | Help: Reference cmake_minimum_required from cmake_policy docsBrad King2014-05-301-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note in a few places of the cmake_policy() command documentation that the cmake_minimum_required() command can set policies too. Inspired-by: Peter Kümmel <syntheticpp@gmx.net>
* | | | | | Help: Format cmake_policy command documentationBrad King2014-05-301-35/+45
|/ / / / / | | | | | | | | | | | | | | | | | | | | Add reStructuredText markup manually to improve formatting of the documentation. Organize the documentation into subsections.
* | | | | Merge topic 'doc-file-command'Brad King2014-05-271-178/+266
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | d74ed543 Help: Format and revise file() command documentation
| * | | | | Help: Format and revise file() command documentationBrad King2014-05-231-178/+266
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Organize the documentation by sub-command to keep the signatures and their descriptions nearby. Use inline and explicit reST markup. Revise wording as necessary for the updated layout. Clarify behavior of the file(GENERATE) command w.r.t. conflicting file names.
* | | | | | Merge topic 'doc-CTEST_BUILD_FLAGS'Brad King2014-05-271-0/+5
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | b8d6ab60 Help: describe CTEST_BUILD_FLAGS
| * | | | | | Help: describe CTEST_BUILD_FLAGSRolf Eike Beer2014-05-231-0/+5
| |/ / / / /
* | | | | | Help: Add a manual for compiler feature control.Stephen Kelly2014-05-271-1/+2
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Link to it from the documentation of related properties, variables and commands. Extend the cmake-developer(7) documentation with notes on extending feature support for compilers.
* | | | | Help: Fix whitespace in doc link.Stephen Kelly2014-05-201-1/+1
| | | | |
* | | | | Features: Extend concept to C language.Stephen Kelly2014-05-141-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add properties and variables corresponding to CXX equivalents. Add features for c_function_prototypes (C90), c_restrict (C99), c_variadic_macros (C99) and c_static_assert (C11). This feature set can be extended later. Add a <PREFIX>_RESTRICT symbol define to WriteCompilerDetectionHeader to conditionally represent the c_restrict feature.
* | | | | Allow the Package Registry to be disabled (#14849)Daniele E. Domenichelli2014-05-122-3/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a project is packaged for redistribution the local package registries should not be updated or consulted. They are for developers. Add variables to disable use of package registries globally: * CMAKE_EXPORT_NO_PACKAGE_REGISTRY that disables the export(PACKAGE) command * CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY that disables the User Package Registry in all the find_package calls. * CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY that disables the System Package Registry in all the find_package calls. Update documentation and unit tests.
* | | | | Add target_compile_features command.Stephen Kelly2014-04-071-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This can be used to set the compiler features required by particular targets. An error is issued at CMake time if the compiler does not support the required feature. If a language dialect flag is required by the features used, that will be added automatically. Base the target_compile_features command on cmTargetPropCommandBase. This gives us 'free' handling of IMPORTED, ALIAS, INTERFACE, non-compilable and missing targets.
* | | | | target_sources: New command to add sources to target.Stephen Kelly2014-04-021-0/+28
| | | | |
* | | | | cmTarget: Allow any generator expression in SOURCES property.Stephen Kelly2014-04-022-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove use of UseObjectLibraries from Makefile and Ninja generators. It is not needed now because those generators use GetExternalObjects which already contains the objects from object libraries. The VS10 generator calls both the UseObjectLibraries and the GetExternalObjects methods. Ensure that duplicates are not created by skipping objects from object libraries in handling of GetExternalObjects. Similarly, fix VS6, VS7 and Xcode object handling by skipping external objects from OBJECT_LIBRARY usage as appropriate. The error message in the BadSourceExpression1 test is now reported by the generator expression evaluator, so it has different text.
* | | | | cmStringCommand: Add GENEX_STRIP subcommand.Stephen Kelly2014-03-311-0/+5
| | | | | | | | | | | | | | | | | | | | Strip out any generator expressions in the input string.
* | | | | add_custom_command: Evaluate generator expressions in DEPENDSStephen Kelly2014-03-201-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rely on evaluation in cmCustomCommandGenerator for the generators. When tracing target dependencies, depend on the union of dependencies for all configurations.
* | | | | Merge topic 'doc-find_package-build-paths'Brad King2014-03-051-0/+1
|\ \ \ \ \ | | |_|_|/ | |/| | | | | | | | | | | | | 69d73d27 Help: Mention in find_package that cmake-gui step is Windows-only (#14781)
| * | | | Help: Mention in find_package that cmake-gui step is Windows-only (#14781)Brad King2014-03-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recently used cmake-gui locations are searched only on Windows because the Windows registry is used to record the values. This behavior is historical and may be removed by a policy in the future so rather than implementing it on other platforms simply document the current behavior.
* | | | | Merge topic 'add_definitions-no-genex'Brad King2014-03-031-4/+2
|\ \ \ \ \ | | |_|_|/ | |/| | | | | | | | | | | | | 1a9316a8 add_definitions: Don't document genex support.
| * | | | add_definitions: Don't document genex support.Stephen Kelly2014-03-031-4/+2
| |/ / / | | | | | | | | | | | | | | | | | | | | This command does not support generator expressions. The documentation was mistakenly extended to claim it in commit v3.0.0-rc1~60^2~3 (Help: Mark up the buildsystem commands documentation, 2014-02-03).
* | | | Merge topic 'install-FILES-genex'Brad King2014-02-241-161/+168
|\ \ \ \ | |_|/ / |/| | / | | |/ | |/| | | | | | | 6e89c8a5 install: Support generator expressions in FILES and PROGRAMS mode f11f7b34 cmInstallFilesGenerator: Add reference to calling cmMakefile e190236c Help: Format install() command documentation
| * | install: Support generator expressions in FILES and PROGRAMS modeBrad King2014-02-211-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | 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: Revise and format add_test() command documentationBrad King2014-02-201-48/+38
|/ | | | | Favor the add_test(NAME) signature and document the limitations of the plain signature.
* 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: Mark up the buildsystem commands documentationStephen Kelly2014-02-069-283/+334
| | | | Cross-link to the cmake-buildsystem manual.
* Help: Use ``inline-literals`` to mark generator expressions.Stephen Kelly2014-02-067-7/+7
|
* project: Manage VERSION variablesBrad King2014-01-291-1/+26
| | | | | | | | | | | | | | | | 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-291-19/+23
| | | | Also add document for CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE variable.
* Help: Fix typo in 'if()' command documentationRaphael Kubo da Costa2014-01-151-1/+1
| | | | s/argumemnts/arguments/
* add_library: Disallow invalid signatures for INTERFACE_LIBRARY.Stephen Kelly2014-01-061-4/+13
| | | | | Document the valid signatures. Add a test for the IMPORTED GLOBAL signature.
* export: Implement EXPORT subcommand (#9822)Stephen Kelly2013-12-241-10/+20
| | | | | | Teach the export command to handle export sets defined by invocations of install(TARGETS ... EXPORT foo). This makes maintenance of targets exported to both the build tree and install tree trivial.
* Help: Clarify if(TARGET) behavior (#14646)Brad King2013-12-181-1/+3
| | | | | Define the meaning of a "target" clearly and link to the commands that create them.
* Help: Format 'if' command documentationBrad King2013-12-181-207/+167
| | | | | | | Manually update reStructuredText formatting. Use a definition list for the possible if() tests supported. Add inline literal markup as appropriate. Also make minor wording tweaks to make it flow better with the new markup.
* Help: Format and clarify source_group() documentation (#14631)Brad King2013-12-051-14/+30
| | | | | Refine the .rst formatting. Document the FILES option explicitly and specify how it treats relative paths.
* Help: Document the CMAKE_FIND_ROOT_PATH* variables.Stephen Kelly2013-11-276-10/+10
| | | | | Add a replacement template for the variables, and link to them from the documentation for the find_* commands.
* Introduce CMAKE_STAGING_PREFIX variable.Stephen Kelly2013-11-211-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | This variable can be useful in cross-compiling contexts where the sysroot is read-only or where the sysroot should otherwise remain pristine. If the new CMAKE_STAGING_PREFIX variable is set, it is used instead of CMAKE_INSTALL_PREFIX when generating the installation rules in cmake_install.cmake. This way, the CMAKE_INSTALL_PREFIX variable always refers to the installation prefix on the target device, regardless of whether host==target. If any -rpath paths passed to the linker contain the CMAKE_STAGING_PREFIX, the matching path fragments are replaced with the CMAKE_INSTALL_PREFIX. Matching paths in the -rpath-link are not transformed. The cross-prefix usr-move workaround is assumed not to require extension regarding CMAKE_STAGING_PREFIX. The staging area is a single prefix, so there is no scope for cross-prefix symlinks. The CMAKE_INSTALL_PREFIX is still used to determine the workaround path, and that variable remains the relevant one even if CMAKE_STAGING_PREFIX is used. If the generated export files are deployed to the target, the workaround will still be in place, and still be employed if required.
* Merge topic 'macro-args-docs'Brad King2013-11-194-14/+51
|\ | | | | | | | | f0db2e3 Help: Document macro argument caveats in more detail
generated by cgit v0.12 at 2025-02-12 09:05:09 (GMT)