| Commit message (Collapse) | Author | Age | Files | Lines |
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The option does not actually participate in argument groups like the
others because it does not actually install anything. Fix the order
in the documentation accordingly.
Reported-by: Daniel Wirtz <daniel.wirtz@simtech.uni-stuttgart.de>
|
| |/
|
|
|
|
| |
Implementation indicates that at least two components of VERSION must
be specified (see Source/cmCMakeMinimumRequired.cxx.) Therefore the
minor version is not optional.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Teach install(DIRECTORY) to support generator expressions in the list
of directories, much like install(FILES) already supports.
|
| |
|
|
|
|
| |
The behaviour of double specified keywords is rather undefined or at
least not clearly documented. This change introduces a strict check and
emits a warning in case a keyword has been specified more than once.
|
| |
|
|
|
|
|
| |
Implement a native `cmake_parse_arguments` command that is fully
compatible with the documented behaviour of the previous implementation.
Leave the CMakeParseArguments module empty but existing for
compatibility.
|
| |\
| |
| |
| |
| | |
194011b8 Help: Add missing parenthesis in add_executable docs
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
5a208f83 Help: Document that file(GLOB*) order is undefined
|
| | |/
| |
| |
| |
| |
| | |
Since this command use 'readdir' under the hood the order of list is
undefined:
* http://stackoverflow.com/questions/8977441/does-readdir-guarantee-an-order
|
| |\ \
| | |
| | |
| | |
| | | |
f19d6a2c Help: Document add_test expectations of test command (#15798)
|
| | |/ |
|
| |/
|
|
|
|
|
| |
CMake assumes that a SHARED library compiled on Windows will export a LIB file.
This is not actually the case on Visual C++ if the library does not export any
symbols, and causes incremental builds to break if the user specifies SHARED
anyway. (Users should use MODULE libraries instead.)
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| | |
4da5a227 Help: document CTEST_CUSTOM_* variables
70c0cc72 ctest_read_custom_files: mention that ctest does this automatically
71c67e83 CTEST_CUSTOM_*: treat variables as lists
936a95d4 CTestCoverageCollectGCOV: replace tabulators
|
| | | |
|
| |/
|
|
|
|
|
| |
Set policy CMP0065 to the value used in the calling project.
Set the the value of CMAKE_ENABLE_EXPORTS if set in the calling
project to initialize the target property appropriately.
|
| |
|
|
|
|
|
|
|
| |
Add documentation and tests for the existing
CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE
CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE
CTest variables.
|
| |
|
|
|
| |
These commands concatenate all their input before matching. Document
this behavior.
|
| |
|
|
|
| |
Add section headers and titles for each command signature. Group
related commands into sections.
|
| |\
| |
| |
| |
| | |
8bfa34b7 Help: Fix typo in get_filename_component docs
|
| | |
| |
| |
| | |
trailing slahes -> trailing slashes
|
| |/
|
|
|
|
|
| |
When more than one value is given to the NAMES option this command by
default will consider one name at a time and search every directory for
it. Add a NAMES_PER_DIR option to tell this command to consider one
directory at a time and search for all names in it.
|
| |
|
|
|
|
| |
In the get_filename_component command, add a new BASE_DIR parameter to
use with the ABSOLUTE and REALPATH options. This will be used when
finding an absolute path from a relative path.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| | |
14e49ed1 if: Add "TEST <test>" condition
623dcc85 ExternalProject: Avoid if() auto-dereference of a "TEST" variable
|
| | |
| |
| |
| |
| |
| |
| |
| | |
if(TEST TestNameThatExists) will return true if a test with the name
TestNameThatExists has been added with add_test. The syntax is similar
to if(TARGET TargetName). Since use of "TEST" as an argument to if()
could previously be interpreted as a non-keyword argument, add policy
CMP0064 to treat it as a keyword as NEW behavior.
|
| |/ |
|
| |\
| |
| |
| |
| | |
eb8eaaec Help: Document Apple Framework creation with an example (#15651)
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Drop the partial documentation of properties from the command
documentation and reference the main properties manual instead.
Otherwise readers may not realize there are many more properties.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a TestLoad setting to CTest that can be set via a new --test-load
command-line option, CTEST_TEST_LOAD variable, or TEST_LOAD option to
the ctest_test command. Teach cmCTestMultiProcessHandler to measure
the CPU load and avoid starting tests that may take more than the
spare load currently available. The expression
<current_load> + <test_processors> <= <max-load>
must be true to start a new test.
Co-Author: Zack Galbreath <zack.galbreath@kitware.com>
|
| |
|
|
| |
s/acorss/across/
|
| |\
| |
| |
| |
| | |
482a3bf3 Help: Document explicitly that policy OLD behavior is deprecated
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The most likely documentation page a project author will read in
response to a policy warning is the page for the policy itself.
Add to every policy documentation page a note explicitly stating
that the OLD behavior is deprecated. Also mention this in the
cmake_policy() command documentation that explains how to set a
policy to OLD.
Suggested-by: Fraser Hutchison <fraser.hutchison@gmail.com>
|
| |\ \
| | |
| | |
| | |
| | | |
c3f40f4f Help: Improve formatting of command documentation
|
| | | |
| | |
| | |
| | |
| | | |
Use inline reStructuredText markup and add cross-references in more
places.
|
| | | |
| | |
| | |
| | |
| | | |
Suggest in the NAMES option that unversioned names go first to prefer
local builds over distro-provided files.
|
| | | |
| | |
| | |
| | |
| | | |
Use inline reStructuredText markup and add cross-references in more
places.
|
| |/ /
| |
| |
| |
| | |
Add dedicated documents for these and link to them instead of
duplicating their documentation in every find command.
|
| |/
|
|
|
|
|
|
|
| |
When documenting in the COMMAND option how to reference an executable,
we previously only explicitly covered how to do it for argv[0] and left
it to the reader to follow the reference to the generator expressions
manual. Add explicit mention of the TARGET_FILE genex in this
documentation since it will be a commonly used generator expression in
this context.
|
| |
|
|
|
|
| |
CMake-generated targets are not supported by add_dependencies. State
this explicitly and use 'install' as an example since this may be
commonly attempted.
|