| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
7361e810 Help: Document COMPONENT option of install(SCRIPT/CODE) (#14956)
|
| | |
|
| |
| |
| |
| |
| | |
Enable the Sphinx 'nitpicky' option and fix the resulting warnings about
dangling references.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Use a bullet list to make it easier to read.
|
|\ \ \ |
|
| | |/
| |/| |
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/
| |
| |
| |
| |
| |
| | |
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.
|
|/ |
|
|\
| |
| |
| |
| | |
d8054987 Help: Fix set_tests_properties documentation typo
|
| |
| |
| |
| | |
The example for FAIL_REGULAR_EXPRESSION should actually name it.
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
e6ba52e8 StringUuid: Mark UPPER flag optional in sub-command synopsis
|
| |/ |
|
|\ \
| |/
|/|
| |
| | |
1fdf4ff0 Help: Suggest in add_custom_command how to create a script (#15112)
|
| | |
|
|\ \
| |/
| |
| |
| | |
412926d0 Help: Clarify add_custom_command multiple command behavior (#15112)
|
| |
| |
| |
| |
| | |
Explicitly say that the commands are not composed into a stateful
script.
|
|/
|
|
|
|
| |
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.
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
Format the reStructuredText markup manually. Organize the command
options into a definition list. Use inline markup to cross-reference
related documents.
|
| |
| |
| |
| |
| | |
Remove leftover generator expression documentation that is now in
the cmake-generator-expressions(7) manual.
|
|/
|
|
| |
Support extraction of UTF-8 strings.
|
|
|
|
| |
Explain that link flags should not be used in transitive contexts.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Use section headers instead of horizontal dividers so that one may link
to the sections.
|
| |
|
|
|
|
|
| |
Add a section for each library type signature. Add a table of contents
at the top for the html builder.
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
907e422b Help: Explain build/install-tree include dirs in more places (#14946)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ |
|
| |\ \ |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
60a981ea Features: Enable compiler extensions by default.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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)
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
2d57a390 Help: Document ctest dashboard client usage
28f73dff Help: Document ctest_start initial checkout command variables
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Describe the behavior of the ctest_start() command when the
CTEST_CHECKOUT_COMMAND or CTEST_CVS_CHECKOUT variable is set.
|