summaryrefslogtreecommitdiffstats
path: root/Help/command
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | Help: Document installed file property APINils Gladitz2014-12-012-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit v3.1.0-rc1~479^2~1 (Add an "installed file" property scope, 2014-05-15) the get_property and set_property commands support an 'INSTALL' scope. Add documentation for this scope.
| * | | | Help: Format set_property and get_property command docsBrad King2014-12-012-28/+42
| |/ / /
* | | | Merge topic 'improve-INTERFACE-property-docs'Brad King2014-11-252-0/+6
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bb1111ea Help: Warn that paths should not be used in INTERFACE_ build properties. 96691d12 Help: Fix typo in genex in documentation. f8f02451 Help: Use a property-specific command instead of the generic one. 8609a884 Help: Make remaining build property docs consistent. bcface39 Help: Link to target_link_libraries from target properies. e12926e7 Help: Format the LINK_INTERFACE_LIBRARIES target properies. c8540e94 Help: Unify the help text of INTERFACE_ build properties.
| * | | | Help: Warn that paths should not be used in INTERFACE_ build properties.Stephen Kelly2014-11-252-0/+6
| | | | |
* | | | | Merge topic 'custom-command-byproducts'Brad King2014-11-252-0/+45
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | 557aef0b ExternalProject: Add options to specify BYPRODUCTS (#14963) e15a7075 Add an option for explicit BYPRODUCTS of custom commands (#14963)
| * | | | Add an option for explicit BYPRODUCTS of custom commands (#14963)Brad King2014-11-142-0/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A common idiom in CMake-based build systems is to have custom commands that generate files not listed explicitly as outputs so that these files do not have to be newer than the inputs. The file modification times of such "byproducts" are updated only when their content changes. Then other build rules can depend on the byproducts explicitly so that their dependents rebuild when the content of the original byproducts really does change. This "undeclared byproduct" approach is necessary for Makefile, VS, and Xcode build tools because if a byproduct were listed as an output of a rule then the rule would always rerun when the input is newer than the byproduct but the byproduct may never be updated. Ninja solves this problem by offering a 'restat' feature to check whether an output was really modified after running a rule and tracking the fact that it is up to date separately from its timestamp. However, Ninja also stats all dependencies up front and will only restat files that are listed as outputs of rules with the 'restat' option enabled. Therefore an undeclared byproduct that does not exist at the start of the build will be considered missing and the build will fail even if other dependencies would cause the byproduct to be available before its dependents build. CMake works around this limitation by adding 'phony' build rules for custom command dependencies in the build tree that do not have any explicit specification of what produces them. This is not optimal because it prevents Ninja from reporting an error when an input to a rule really is missing. A better approach is to allow projects to explicitly specify the byproducts of their custom commands so that no phony rules are needed for them. In order to work with the non-Ninja generators, the byproducts must be known separately from the outputs. Add a new "BYPRODUCTS" option to the add_custom_command and add_custom_target commands to specify byproducts explicitly. Teach the Ninja generator to specify byproducts as outputs of the custom commands. In the case of POST_BUILD, PRE_LINK, and PRE_BUILD events on targets that link, the byproducts must be specified as outputs of the link rule that runs the commands. Activate 'restat' for such rules so that Ninja knows it needs to check the byproducts, but not for link rules that have no byproducts.
* | | | | Merge topic 'doc-target_include_directories-fixup'Brad King2014-11-171-2/+2
|\ \ \ \ \ | | |_|_|/ | |/| | | | | | | | | | | | | 1d22ee67 Help: target_include_directories does not allow target names
| * | | | Help: target_include_directories does not allow target namesBrad King2014-11-171-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit v2.8.11~227^2~1 (Don't allow targets args in the new target commands, 2013-01-29) the target_include_directories command does not support target names on the right hand side, but that commit forgot to remove it from the docs. It was never released with such support. Update the command documentation now.
* | | | | Merge topic 'console-pool'Brad King2014-11-172-3/+16
|\ \ \ \ \ | | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2d75d7e5 Help: Add notes for topic 'console-pool' f42d86f0 Ninja: Implement USES_TERMINAL using the console pool if available f281ae01 Ninja: Remove unused declaration d5eae556 Ninja: factor out the test for console pool support 4d1fedf4 Give the interactive cache editor the USES_TERMINAL property fe5d6e8c Add USES_TERMINAL option for custom commands ad6ee426 Rename doing_verbatim to doing_nothing
| * | | | Add USES_TERMINAL option for custom commandsPeter Collingbourne2014-11-142-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Teach the add_custom_command and add_custom_target commands a new USES_TERMINAL option. Use it to tell the generator to give the command direct access to the terminal if possible.
* | | | | Merge topic 'string-SUBSTRING-truncate'Brad King2014-11-171-1/+6
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | 474bbb9d string: Tolerate SUBSTRING length exceeding end index
| * | | | string: Tolerate SUBSTRING length exceeding end indexDomen Vrankar2014-11-131-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | string SUBSTRING command now ignores length if it points past end of string and uses end of string instead. String SUBSTRING tests now cover more corner cases.
* | | | | Help: Document add_custom_command marking outputs GENERATEDBrad King2014-11-141-0/+2
| | | | |
* | | | | Help: Revise and format 'add_custom_target' docsBrad King2014-11-131-29/+64
|/ / / / | | | | | | | | | | | | | | | | | | | | Format the reStructuredText markup manually. Organize the command options into a definition list. Use inline markup to cross-reference related documents.
* | | | Merge topic 'doc-install-SCRIPT-CODE-COMPONENT'Brad King2014-11-131-1/+2
|\ \ \ \ | |_|/ / |/| | / | | |/ | |/| 7361e810 Help: Document COMPONENT option of install(SCRIPT/CODE) (#14956)
| * | Help: Document COMPONENT option of install(SCRIPT/CODE) (#14956)Brad King2014-11-131-1/+2
| |/
* | Help: Fix broken cross-references reported by 'nitpicky' optionBrad King2014-11-072-3/+3
| | | | | | | | | | Enable the Sphinx 'nitpicky' option and fix the resulting warnings about dangling references.
* | Merge branch 'release-doc-formatting' into releaseBrad King2014-11-071-8/+11
|\ \
| * | Help: Format add_library documented list of INTERFACE commandsBrad King2014-11-061-8/+11
| | | | | | | | | | | | Use a bullet list to make it easier to read.
* | | Merge branch 'doc-add_library-typo' into releaseBrad King2014-10-311-1/+1
|\ \ \
| * | | Documentation: Fix minor typo thecommand -> the commandNils Gladitz2014-10-311-1/+1
| | |/ | |/|
* | | Merge branch 'doc-add_compile_options' into releaseBrad King2014-10-292-11/+14
|\ \ \ | |_|/ |/| |
| * | Help: Reference add_compile_options from add_definitions (#15225)Brad King2014-10-291-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | When we explain in add_definitions documentation that it is intended only for preprocessor definitions, link to add_compile_options for adding other flags. Also explicitly mention that the order of add_definitions calls with respect to target creation does not matter. This differs from the behavior now explicitly stated in the documentation of add_compile_options.
| * | Help: Clarify add_compile_options documentation (#15225)Brad King2014-10-291-7/+8
| |/ | | | | | | | | | | | | Explain that it affects only targets added after the call. Fix the link to the COMPILE_OPTIONS directory propert documentation. Update the latter to explain that it is used to initialize the corresponding target property when a target is created.
* | Help: Wrap long ctest_submit signature lineBrad King2014-10-221-1/+5
|/
* Merge topic 'doc-set_test_properties-example'Brad King2014-09-151-1/+1
|\ | | | | | | | | d8054987 Help: Fix set_tests_properties documentation typo
| * Help: Fix set_tests_properties documentation typoAndrew Bauer2014-09-121-1/+1
| | | | | | | | The example for FAIL_REGULAR_EXPRESSION should actually name it.
* | Merge topic 'if-sanity'Brad King2014-09-151-0/+6
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 858d5a0b Fix if() checks of CMAKE_SYSTEM_NAME on Cygwin e177e7af FPHSA: Avoid if() dereferencing of quoted variable 425acc52 cmcurl: Use if(DEFINED) to simplify conditions cede5cbd libarchive: Avoid depending on if() to dereference a quoted variable 2d97178b FindGTK2: Avoid depending on if() to dereference a quoted variable 0b12815d Modules/Test*.cmake: Use if(DEFINED) to simplify conditions 188a1f23 If: Introduce policy CMP0054 - don't dereference quoted variables in if() b900c1cc If: Extract cmConditionEvaluator from if() implementation
| * If: Introduce policy CMP0054 - don't dereference quoted variables in if()Nils Gladitz2014-09-111-0/+6
| |
* | Merge topic 'string-uuid-doc-fix'Brad King2014-09-101-1/+1
|\ \ | | | | | | | | | | | | e6ba52e8 StringUuid: Mark UPPER flag optional in sub-command synopsis
| * | StringUuid: Mark UPPER flag optional in sub-command synopsisNils Gladitz2014-09-101-1/+1
| |/
* | Merge topic 'doc-add_custom_command-multiple-commands'Brad King2014-09-091-0/+3
|\ \ | |/ |/| | | | | 1fdf4ff0 Help: Suggest in add_custom_command how to create a script (#15112)
| * Help: Suggest in add_custom_command how to create a script (#15112)Brad King2014-09-081-0/+3
| |
* | Merge topic 'doc-add_custom_command-multiple-commands'Brad King2014-09-041-1/+2
|\ \ | |/ | | | | | | 412926d0 Help: Clarify add_custom_command multiple command behavior (#15112)
| * Help: Clarify add_custom_command multiple command behavior (#15112)Brad King2014-09-021-1/+2
| | | | | | | | | | Explicitly say that the commands are not composed into a stateful script.
* | Help: Clarify --debug-trycompile usage with try_compileAlan W. Irwin2014-09-031-3/+4
|/ | | | | | Explain that try_compile calls need to be protected with conditions to avoid running more than once so that it is easy to isolate a single try_compile to perform with --debug-trycompile.
* StringUuid: Implement new string(UUID) sub-command.Nils Gladitz2014-08-281-0/+12
|
* Merge topic 'doc-add_custom_command'Brad King2014-08-061-121/+124
|\ | | | | | | | | | | | | 5bf1c5cc Help: Document add_custom_command PRE_BUILD/PRE_LINK for exe/lib only (#15059) 2a58c872 Help: Revise and format 'add_custom_command' docs cb88742d Help: Remove stray content from 'add_custom_command' docs
| * Help: Document add_custom_command PRE_BUILD/PRE_LINK for exe/lib only (#15059)Brad King2014-08-051-0/+2
| | | | | | | | | | | | | | State explicitly that the PRE_LINK mode is not for targets created by the add_custom_target command. The existing wording for PRE_BUILD being treated as PRE_LINK by non-VS generators will now imply this restriction for PRE_BUILD too.
| * Help: Revise and format 'add_custom_command' docsBrad King2014-08-051-97/+122
| | | | | | | | | | | | Format the reStructuredText markup manually. Organize the command options into a definition list. Use inline markup to cross-reference related documents.
| * Help: Remove stray content from 'add_custom_command' docsBrad King2014-08-051-24/+0
| | | | | | | | | | Remove leftover generator expression documentation that is now in the cmake-generator-expressions(7) manual.
* | file: Add ENCODING option to file(STRINGS) command (#10519)Clinton Stimpson2014-08-061-0/+3
|/ | | | Support extraction of UTF-8 strings.
* Help: Clarify target_link_libraries treatment of flags (#15034)Brad King2014-07-281-1/+4
| | | | Explain that link flags should not be used in transitive contexts.
* add_library: Allow arbitrary non-linked sources in OBJECT librariesBrad King2014-07-091-1/+2
| | | | | | | | | | | Loosen this restriction on OBJECT libraries to allow source files of any name to be generated by custom commands or listed for reference in IDE projects so long as they would not affect linking of a normal library. Update the rejection message to be more specific about the looser restriction. Extend the ObjectLibrary test to cover a ".cmake" file generated by a custom command in an OBJECT library.
* install(DIRECTORY): Add MESSAGE_NEVER option to avoid output (#13761)Brad King2014-06-241-1/+3
| | | | | | | | | | | | Installing large directories, e.g., the output of a doxygen run, prints one line per file resulting in too much noise in the build output. Add an option to the install(DIRECTORY) command to not print anything upon make install. Extend the RunCMake.install test with cases covering MESSAGE_NEVER behavior of the install(DIRECTORY) command. Suggested-by: Stefan Eilemann <Stefan.Eilemann@epfl.ch>
* install: Add CMAKE_INSTALL_MESSAGE variable (#13761)Brad King2014-06-242-1/+6
| | | | | | | | | Create a variable to allow users to control which installation messages are printed. In particular, provide a "LAZY" setting that prints "Installing" messages but not "Up-to-date" messages. This is desirable for incremental re-installations. Suggested-by: J Decker <d3ck0r@gmail.com>
* Help: Add install() command document section headersBrad King2014-06-241-5/+17
| | | | | Use section headers instead of horizontal dividers so that one may link to the sections.
* Help: Link to Object Library docs from add_libraryBrad King2014-06-121-2/+2
|
* Help: Organize add_library command documentationBrad King2014-06-121-4/+15
| | | | | Add a section for each library type signature. Add a table of contents at the top for the html builder.
* Help: Mention INTERFACE_SOURCES as settable for INTERFACE libsBrad King2014-06-121-2/+3
| | | | | | | The add_library(INTERFACE) and Interface Libraries documentation list all the INTERFACE_* properties and target_* commands that can be used to define the interface. Add INTERFACE_SOURCES and target_sources() to these lists for completeness.
generated by cgit v0.12 at 2025-04-05 12:55:59 (GMT)