| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| | |
e462ef74 Help: Add notes for topic 'cmake-gui-osx-install-command-line'
8ea2db26 cmake-gui: Replace command-line install dialog with information box
438ce4a0 cmake-gui: Add --install option to add command-line tools on OS X
41477d5c cmake-gui: Drop undocumented and unused --mac-install option
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
b0ea3673 Help: Spell '-D' option consistently across documentation (#15575)
|
| |/
| |
| |
| |
| |
| | |
Always show the option with its argument separate in summary text.
State in the main documentation that the option and its argument can be
given together too.
|
|\ \
| | |
| | |
| | |
| | | |
7412d100 Help: Fix typo in cmake-buildsystem(7) manual
|
| |/ |
|
|/
|
|
|
|
| |
Create a <LANG>_INCLUDE_WHAT_YOU_USE target property (initialized by a
CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE variable) to specify an IWYU command
line to be run along with the compiler.
|
|\
| |
| |
| |
| |
| | |
342d15cb Update packaging of CMake for QtIFW 2.0
9a0ba4d2 CPackIFW: Add QtIFW 2.0 support
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add variables:
- CPACK_IFW_FRAMEWORK_VERSION
- CPACK_IFW_PACKAGE_ALLOW_NON_ASCII_CHARACTERS
- CPACK_IFW_PACKAGE_ALLOW_SPACE_IN_PATH
- CPACK_IFW_PACKAGE_CONTROL_SCRIPT
- CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_INI_FILE
- CPACK_IFW_PACKAGE_MAINTENANCE_TOOL_NAME
- CPACK_IFW_PACKAGE_START_MENU_DIRECTORY
- CPACK_IFW_VERBOSE
|
| |
| |
| |
| |
| | |
Add a note to the cmake_minimum_required documentation about the
limits of calling it in a function.
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
226df303 CTest: Stop telling 'make' to ignore errors with -i
28e7a135 Help: Fix build_command alternative signature docs
231601b6 build_command: Choose configuration consistently across signatures
|
| |
| |
| |
| | |
Add policy CMP0061 to maintain compatibility for existing projects.
|
| |
| |
| |
| |
| | |
Do not specify that --config will not be added, because the
command does add it.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
1237d5fa Help: Add notes for topic 'cpack-deb-component-dependencies'
e3f522f6 CPack/DEB per component dependencies
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
1506f9ca find_package: Drop search in recent cmake-gui locations
8d484463 FindFLTK: Drop search in recent cmake-gui locations
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The find_package command, on Windows, has always searched build trees
recently visited by cmake-gui (or CMakeSetup at one time). This was
done when the command was created with the intention of simplifying
workflows involving building multiple dependent projects. However,
this behavior depends on recent developer interaction and therefore
can create different find results based on transient system states.
It can lead to surprising results and user confusion.
Since this behavior was first added CMake has gained many more search
options, better error messages when a package is not found, and a
package registry. The latter in particular allows projects to make
their build trees available for dependent projects to find without
user intervention. Therefore the originally intended workflow can
be achieved in other, more stable ways.
After the above evoluion of find_package we have now decided that
the magic search-where-cmake-gui-was behavior does more harm than
good. Drop it. We do not need a policy for this behavior change
because it only affects interactive use.
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
f39d26ca Help: Clarify file(COPY) directory semantics (#15561)
|
| |/
| |
| |
| | |
State explicitly that directory structure is preserved.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
695d6f62 Help: Revise ctest_* command documentation (#15559)
f8716c8b Help: Update cmake-generators(7) organization for GHS
|
| | |
| | |
| | |
| | |
| | |
| | | |
Revise documentation for the major dashboard client step ``ctest_*``
commands. Modernize the documentation formatting. Add some missing
options.
|
| |/ |
|
|/
|
|
|
|
|
| |
Use the KWSys Process "MergeOutput" option to give the child process
the same pipe (or file) for both stdout and stderr. This allows
natural merging of stdout and stderr together instead of merging
on arbitrary buffered read boundaries as before.
|
|\
| |
| |
| |
| |
| |
| | |
5731fb2e ctest_build: mention CTEST_BUILD_COMMAND in the docs
753da8c6 ctest_build: update the default target documentation
5ab896ae ctest_build: spruce up the documentation a bit
|
| | |
|
| | |
|
| |
| |
| |
| | |
Adds markup and links to other sections.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
a6e4e73d VS: Add option to put INSTALL target in .sln default build
562e69dd Tests: Enable devenv tests on VS >= 10
|
| |/
| |
| |
| |
| | |
Add a CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD variable to control
this behavior.
|
|/
|
|
| |
Dependency auto-discovery can now be set per component
|
|\
| |
| |
| |
| | |
aed6239e if: Implement new IN_LIST operator
|
| | |
|
|\ \
| |/
| |
| |
| | |
32a2f414 Revert "add_custom_command: Diagnose MAIN_DEPENDENCY limitation."
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 242c3966 (add_custom_command: Diagnose
MAIN_DEPENDENCY limitation, 2015-03-09) and the follow up commit
b372a99a (UseSWIG: Do not use MAIN_DEPENDENCY on custom commands,
2015-03-26).
I misdiagnosed the underlying issue that prompted creation of policy CMP0057.
The actual issue surfaces when a single custom command's MAIN_DEPENDENCY
is listed in more than one target; this issue will have to be addressed
independently.
|
|\ \
| | |
| | |
| | |
| | | |
9535b86d Help: Replace CMP0054 example to show when it makes a difference
|
| | |
| | |
| | |
| | |
| | |
| | | |
The previous example for CMP0054 did not show how critical the policy is
since the result is the same in both cases (NEW and OLD behavior).
Instead show an example when the policy does make a difference.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
d401aa21 Help: Revise buildsystem artifact file type documentation (#15539)
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
Add sections to the cmake-buildsystem(7) manual and cross-reference
them with relevant variables and target properties. This avoids
duplicating the information and allows it to be more detailed.
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
6ac3712d Help: Document that cmake_minimum_required should be called first
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Many projects put their project() call first, but the actions taken
by this command can be influenced by policies and other information
set by a call to cmake_minimum_required. Document in each of these
two commands that cmake_minimum_required should be called first.
Suggested-by: Alan W. Irwin
|
|\ \
| |/
|/|
| |
| | |
853ef717 Help: Clarify policy CMP0026 title
|
| |
| |
| |
| |
| |
| |
| | |
Clarify that the policy only applies to build targets and
not e.g. imported targets.
Suggested-by: Alan W. Irwin
|
|\ \
| | |
| | |
| | |
| | | |
1b03332e Help: Clarify that CMAKE_SIZEOF_VOID_P is specific to the target machine
|
| |/ |
|
|/
|
|
|
|
|
|
|
| |
The documentation of this variable in the CTest module is outdated
and has been superseded by the ctest(1) manual. In particular, the
latter mentions that it works with the Ninja generator as well as
makefile generators. Remove the documentation from the CTest module
and replace it with a link to the main variable documentation (which
already references the ctest(1) manual).
|
|\
| |
| |
| |
| |
| |
| |
| | |
b470d618 Help: Add notes for topic 'ExternalProject-genex'
0273ef14 ExternalProject: Allow generator expressions with LOG_* options (#15287)
7bd8cfb8 ExternalProject: Allow generator expressions in initial cache options
1cf43dcf Tests: Add case to cover ExternalProject with subdirectories
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
a61e0994 Help: Fix formatting of env var refs in ctest.1 manual
|
| |/ |
|