summaryrefslogtreecommitdiffstats
path: root/Help
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'ctest-no-make-i'Brad King2015-05-124-2/+35
|\ | | | | | | | | | | | | 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
| * CTest: Stop telling 'make' to ignore errors with -iBrad King2015-05-124-1/+34
| | | | | | | | Add policy CMP0061 to maintain compatibility for existing projects.
| * Help: Fix build_command alternative signature docsBrad King2015-05-121-1/+1
| | | | | | | | | | Do not specify that --config will not be added, because the command does add it.
* | Merge topic 'cpack-deb-component-dependencies'Brad King2015-05-121-0/+6
|\ \ | | | | | | | | | | | | | | | 1237d5fa Help: Add notes for topic 'cpack-deb-component-dependencies' e3f522f6 CPack/DEB per component dependencies
| * | Help: Add notes for topic 'cpack-deb-component-dependencies'Brad King2015-05-121-0/+6
| |/
* | Merge topic 'find_package-no-cmake-gui-paths'Brad King2015-05-122-11/+15
|\ \ | | | | | | | | | | | | | | | 1506f9ca find_package: Drop search in recent cmake-gui locations 8d484463 FindFLTK: Drop search in recent cmake-gui locations
| * | find_package: Drop search in recent cmake-gui locationsBrad King2015-05-082-11/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Merge topic 'doc-file-COPY-preserves-structure'Brad King2015-05-121-1/+5
|\ \ \ | |_|/ |/| | | | | | | | f39d26ca Help: Clarify file(COPY) directory semantics (#15561)
| * | Help: Clarify file(COPY) directory semantics (#15561)Brad King2015-05-081-1/+5
| |/ | | | | | | State explicitly that directory structure is preserved.
* | Merge topic 'doc-ctest-command-formatting'Brad King2015-05-089-162/+285
|\ \ | | | | | | | | | | | | | | | 695d6f62 Help: Revise ctest_* command documentation (#15559) f8716c8b Help: Update cmake-generators(7) organization for GHS
| * | Help: Revise ctest_* command documentation (#15559)Brad King2015-05-078-159/+282
| | | | | | | | | | | | | | | | | | Revise documentation for the major dashboard client step ``ctest_*`` commands. Modernize the documentation formatting. Add some missing options.
| * | Help: Update cmake-generators(7) organization for GHSBrad King2015-05-071-3/+3
| |/
* | execute_process: Improve stdout/stderr mergingBrad King2015-05-072-1/+7
|/ | | | | | | 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.
* Merge topic 'update-ctest_build-docs'Brad King2015-05-071-14/+16
|\ | | | | | | | | | | | | 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
| * ctest_build: mention CTEST_BUILD_COMMAND in the docsBen Boeckel2015-05-071-4/+5
| |
| * ctest_build: update the default target documentationBen Boeckel2015-05-071-1/+2
| |
| * ctest_build: spruce up the documentation a bitBen Boeckel2015-05-071-12/+12
| | | | | | | | Adds markup and links to other sections.
* | Merge topic 'vs-install-in-default-build'Brad King2015-05-073-0/+16
|\ \ | | | | | | | | | | | | | | | a6e4e73d VS: Add option to put INSTALL target in .sln default build 562e69dd Tests: Enable devenv tests on VS >= 10
| * | VS: Add option to put INSTALL target in .sln default buildRobert Goulet2015-05-063-0/+16
| |/ | | | | | | | | Add a CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD variable to control this behavior.
* | CPack/DEB component dependency auto-discoveryRaffi Enficiaud2015-05-071-0/+6
|/ | | | Dependency auto-discovery can now be set per component
* Merge topic 'if-IN_LIST'Brad King2015-04-303-1/+19
|\ | | | | | | | | aed6239e if: Implement new IN_LIST operator
| * if: Implement new IN_LIST operatorNils Gladitz2015-04-303-1/+19
| |
* | Merge topic 'revert-CMP0057'Brad King2015-04-302-24/+1
|\ \ | |/ | | | | | | 32a2f414 Revert "add_custom_command: Diagnose MAIN_DEPENDENCY limitation."
| * Revert "add_custom_command: Diagnose MAIN_DEPENDENCY limitation."Nils Gladitz2015-04-302-24/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Merge topic 'doc-CMP0054-example'Brad King2015-04-301-6/+10
|\ \ | | | | | | | | | | | | 9535b86d Help: Replace CMP0054 example to show when it makes a difference
| * | Help: Replace CMP0054 example to show when it makes a differenceTamás Kenéz2015-04-291-6/+10
| | | | | | | | | | | | | | | | | | 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.
* | | Merge topic 'doc-target-file-types'Brad King2015-04-3023-49/+161
|\ \ \ | | | | | | | | | | | | | | | | d401aa21 Help: Revise buildsystem artifact file type documentation (#15539)
| * | | Help: Revise buildsystem artifact file type documentation (#15539)Brad King2015-04-2923-49/+161
| | |/ | |/| | | | | | | | | | | | | 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.
* | | Merge topic 'doc-cmake_minimum_required-first'Brad King2015-04-302-0/+14
|\ \ \ | |_|/ |/| | | | | | | | 6ac3712d Help: Document that cmake_minimum_required should be called first
| * | Help: Document that cmake_minimum_required should be called firstBrad King2015-04-292-0/+14
| |/ | | | | | | | | | | | | | | | | 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
* | Merge topic 'CMP0026-doc-title'Brad King2015-04-291-1/+1
|\ \ | |/ |/| | | | | 853ef717 Help: Clarify policy CMP0026 title
| * Help: Clarify policy CMP0026 titleNils Gladitz2015-04-281-1/+1
| | | | | | | | | | | | | | Clarify that the policy only applies to build targets and not e.g. imported targets. Suggested-by: Alan W. Irwin
* | Merge topic 'doc-sizeof_void_p'Brad King2015-04-281-1/+1
|\ \ | | | | | | | | | | | | 1b03332e Help: Clarify that CMAKE_SIZEOF_VOID_P is specific to the target machine
| * | Help: Clarify that CMAKE_SIZEOF_VOID_P is specific to the target machineNils Gladitz2015-04-231-1/+1
| |/
* | ctest: Consolidate documentation of CTEST_USE_LAUNCHERS (#15533)Brad King2015-04-281-2/+5
|/ | | | | | | | | 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).
* Merge topic 'ExternalProject-genex'Brad King2015-04-221-0/+6
|\ | | | | | | | | | | | | | | 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
| * Help: Add notes for topic 'ExternalProject-genex'Brad King2015-04-211-0/+6
| |
* | Merge topic 'doc-ctest-env-formatting'Brad King2015-04-221-2/+4
|\ \ | | | | | | | | | | | | a61e0994 Help: Fix formatting of env var refs in ctest.1 manual
| * | Help: Fix formatting of env var refs in ctest.1 manualBrad King2015-04-221-2/+4
| |/
* | Help: Document in find_library how to search for static librariesBrad King2015-04-221-0/+6
|/ | | | | This has been implemented since commit v2.6.0~295 (Make find_library test for the library file as named, 2008-02-06). Add the docs.
* Merge topic 'cpack-rpm-refactored-file-listing'Brad King2015-04-211-0/+6
|\ | | | | | | | | | | | | cd953bf7 Help: Add notes for topic 'cpack-rpm-refactored-file-listing' 76080c32 CPackRPM content listing refactor 152e9b32 CPackRPM package content list code move
| * Help: Add notes for topic 'cpack-rpm-refactored-file-listing'Brad King2015-04-201-0/+6
| |
* | Merge topic 'add-GreenHills-MULTI-generator'Brad King2015-04-2011-0/+66
|\ \ | | | | | | | | | | | | | | | | | | 66b641f4 Help: Add notes for topic 'add-GreenHills-MULTI-generator' 48004d9d Add a 'Green Hills MULTI' generator on Windows 051d8be1 cmLocalGenerator: Constify some cmTarget and cmGeneratorTarget arguments
| * | Help: Add notes for topic 'add-GreenHills-MULTI-generator'Brad King2015-04-201-0/+8
| | |
| * | Add a 'Green Hills MULTI' generator on WindowsGeoff Viola2015-04-2010-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Green Hills MULTI is an IDE for embedded real-time systems. The IDE's product page can be found here: http://www.ghs.com/products/MULTI_IDE.html It supports cross compiling on ARM, Intel x86, and other architectures with various operating systems. The IDE exists on Linux and Windows host systems, but CMake will currently only generate the project files on Windows host systems.
* | | Help: Clarify PDB_NAME fallback behavior (#15518)Brad King2015-04-171-1/+2
| |/ |/| | | | | It uses the OUTPUT_NAME if set, not always the target name.
* | Merge topic 'FPHSA-updates'Brad King2015-04-171-0/+10
|\ \ | | | | | | | | | | | | | | | | | | 84f06d0c FPHSA: Document REQUIRED_VARS recommendation (#15352) a3ad275c FPHSA: Revise and format documentation d1a6d15b FPHSA: Always populate the ExactCase_FOUND variable (#15412).
| * | FPHSA: Always populate the ExactCase_FOUND variable (#15412).Stephen Kelly2015-04-171-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The UPPERCASE name was inconsistent with config-packages, the find_dependency macro, and even FPHSA itself, which expects components to be specified with names matching ExactCase. The FOUND_VAR was only permitted to have two possible values, and now both are set for compatibility. Document it as obsolete, and adjust the code for the same. Users of the variable should just remove it.
* | | Merge topic 'vs10-no-macros'Brad King2015-04-161-0/+9
|\ \ \ | | | | | | | | | | | | | | | | 885ab9ab VS: Drop reload macros for VS >= 10 (#11258,#14680)
| * | | VS: Drop reload macros for VS >= 10 (#11258,#14680)Brad King2015-04-151-0/+9
| |/ / | | | | | | | | | | | | | | | | | | | | | We never implemented them for VS 11 (2012), 12 (2013), or 14 (2015). For VS 10 (2010) the reload macro does not work correctly when run from inside a build launched through the IDE because stopping the build kills the CMake that is driving the reload. Fortunately VS >= 10 know how to reload the whole solution anyway.
generated by cgit v0.12 at 2024-09-24 16:35:39 (GMT)