summaryrefslogtreecommitdiffstats
path: root/Help
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'ctest-test-load'Brad King2015-07-026-0/+40
|\ | | | | | | | | | | | | | | f62d301b ctest: Optionally avoid starting tests that may exceed a given CPU load 07c550ca cmCTestMultiProcessHandler: Refactor RUN_SERIAL implementation 8bf5a80b cmSystemTools: Add StringToULong helper dffc307c Tests: Teach RunCMake infrastructure to optionally timeout
| * ctest: Optionally avoid starting tests that may exceed a given CPU loadBetsy McPhail2015-06-306-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Merge topic 'doc-find-path-variables'Brad King2015-06-2514-97/+88
|\ \ | |/ |/| | | | | 3117b5fe Help: Revise CMAKE_*_PATH and CMAKE_SYSTEM_*_PATH variable docs (#15631)
| * Help: Revise CMAKE_*_PATH and CMAKE_SYSTEM_*_PATH variable docs (#15631)Brad King2015-06-2514-97/+88
| | | | | | | | | | Improve reStructuredText formatting and cross-references. Specify explicitly that each variable may be set to a ;-list of multiple values.
* | Help: Fix typo in ctest_test documentationZack Galbreath2015-06-241-1/+1
| | | | | | | | s/acorss/across/
* | Merge topic 'doc-cmake-buildsystem-typo'Brad King2015-06-221-1/+1
|\ \ | | | | | | | | | | | | 17c51521 Help: Fix a typo in cmake-buildsystem(7) manual
| * | Help: Fix a typo in cmake-buildsystem(7) manualErik Sjölund2015-06-221-1/+1
| |/ | | | | | | | | Add the property name INTERFACE_INCLUDE_DIRECTORIES that was missing from a set_property command.
* | Merge topic 'GNUInstallDirs-special-prefixes'Brad King2015-06-191-0/+9
|\ \ | | | | | | | | | | | | | | | | | | 8bcec4d2 Help: Add notes for topic 'GNUInstallDirs-special-prefixes' c8bd37ec GNUInstallDirs: Add special cases for certain prefixes 5f30f175 GNUInstallDirs: Add test cases
| * | Help: Add notes for topic 'GNUInstallDirs-special-prefixes'Brad King2015-06-181-0/+9
| | |
* | | Merge topic 'ConcurrentFortran-compiler-id'Brad King2015-06-192-0/+6
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 54676a0e Help: Add notes for topic 'ConcurrentFortran-compiler-id' 7cd539b1 Add support for Concurrent Fortran 77 Compiler 0d204c1c CMakeDetermineCompilerId: Try matching compiler output to detect id 5f0dad75 CMakeDetermineCompilerId: Refactor id build/check loop logic c65a060e CMakeDetermineCompilerId: Optionally try some flags before no flags
| * | | Help: Add notes for topic 'ConcurrentFortran-compiler-id'Brad King2015-06-181-0/+5
| | | |
| * | | Add support for Concurrent Fortran 77 CompilerBrad King2015-06-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Concurrent Fortran compiler (ccur.com) is available on Linux and can be used much like the GNU Fortran compiler. Currently it has no preprocessor symbols to identify it so we need to detect it by matching compiler output. Suggested-by: Anthony Ette <Anthony.R.Ette@controlsdata.com>
* | | | Merge topic 'doc-CMAKE_GENERATOR_PLATFORM-typo'Brad King2015-06-191-1/+1
|\ \ \ \ | |/ / / |/| | | | | | | | | | | 1c9db7db Help: Fix typo in CMAKE_GENERATOR_PLATFORM docs (#15621)
| * | | Help: Fix typo in CMAKE_GENERATOR_PLATFORM docs (#15621)Brad King2015-06-181-1/+1
| | |/ | |/| | | | | | | s/toolset/platform/
* | | Merge topic 'compiler-launcher'Brad King2015-06-155-0/+29
|\ \ \ | |_|/ |/| | | | | | | | 698f7597 Add options to launch the compiler through tools like ccache or distcc
| * | Add options to launch the compiler through tools like ccache or distccBill Hoffman2015-06-155-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Create a <LANG>_COMPILER_LAUNCHER target property (initialized by a CMAKE_<LANG>_COMPILER_LAUNCHER variable) to specify a compiler launcher tool. This will supersede the CMAKE_<LANG>_COMPILER_ARG1 approach to using such tools. The old approach set CMAKE_<LANG>_COMPILER to the launcher tool while the new approach leaves this variable set to the actual compiler. Implement this property for Makefile and Ninja generators. It cannot be implemented for VS or Xcode generators as the IDE build tools offer no such hooks.
* | | Merge topic 'FindBISON-DEFINES_FILE'Brad King2015-06-111-0/+6
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6863c0d5 Help: Add notes for topic 'FindBISON-DEFINES_FILE' 12e534c2 FindBISON: Add DEFINES_FILE option to pass --defines=FILE eb859263 FindBISON: Use CMAKE_PARSE_ARGUMENTS to parse arguments 29985ad8 FindBISON: Use BISON_TARGET macro argument names internally 801b799f FindBISON: Improve documentation formatting
| * | | Help: Add notes for topic 'FindBISON-DEFINES_FILE'Brad King2015-06-111-0/+6
| | | |
* | | | Merge topic 'doc-policy-OLD-deprecated'Brad King2015-06-0967-5/+139
|\ \ \ \ | |/ / / |/| | | | | | | | | | | 482a3bf3 Help: Document explicitly that policy OLD behavior is deprecated
| * | | Help: Document explicitly that policy OLD behavior is deprecatedBrad King2015-06-0967-5/+139
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | | Merge topic 'doc-formatting'Brad King2015-06-0959-345/+352
|\ \ \ | | | | | | | | | | | | | | | | c3f40f4f Help: Improve formatting of command documentation
| * | | Help: Improve formatting of command documentationMichael Scott2015-06-0859-345/+352
| | | | | | | | | | | | | | | | | | | | Use inline reStructuredText markup and add cross-references in more places.
* | | | Merge topic 'doc-find-versioned-location'Brad King2015-06-091-0/+5
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 7ab0806f Help: Document find_* command versioned/unversioned name ordering
| * | | | Help: Document find_* command versioned/unversioned name orderingBrad King2015-06-081-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | Suggest in the NAMES option that unversioned names go first to prefer local builds over distro-provided files.
* | | | | Merge topic 'doc-find-command-cleanup'Brad King2015-06-0913-119/+184
|\ \ \ \ \ | |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3de3544f Help: Improve documentation formatting of find_* commands 8c64c478 Help: Document CMAKE_FIND_APPBUNDLE and CMAKE_FIND_FRAMEWORK 25b4483e Help: Document CMAKE_SYSTEM_APPBUNDLE_PATH variable e2f34986 Help: Document CMAKE_SYSTEM_FRAMEWORK_PATH variable
| * | | | Help: Improve documentation formatting of find_* commandsBrad King2015-06-086-90/+114
| | | | | | | | | | | | | | | | | | | | | | | | | Use inline reStructuredText markup and add cross-references in more places.
| * | | | Help: Document CMAKE_FIND_APPBUNDLE and CMAKE_FIND_FRAMEWORKBrad King2015-06-086-29/+53
| | | | | | | | | | | | | | | | | | | | | | | | | Add dedicated documents for these and link to them instead of duplicating their documentation in every find command.
| * | | | Help: Document CMAKE_SYSTEM_APPBUNDLE_PATH variableBrad King2015-06-082-0/+8
| | | | |
| * | | | Help: Document CMAKE_SYSTEM_FRAMEWORK_PATH variableBrad King2015-06-082-0/+9
| |/ / /
* | | | Merge topic 'doc-drop-incorrect-cmake-developer-advice'Brad King2015-06-091-1/+0
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 972853b1 Help: Drop incorrect advice from cmake-developer.7 manual
| * | | | Help: Drop incorrect advice from cmake-developer.7 manualBrad King2015-06-081-1/+0
| | |/ / | |/| | | | | | | | | | | | | | Drop the comment on the purpose of PATH_SUFFIXES in our Find Module example. It was incorrect.
* | | | Merge topic 'revert-mingw-no-find_library-dll'Brad King2015-06-091-6/+0
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | f5dbf00d Windows-GNU: Restore find_library treatment of '.dll' as linkable (#15409)
| * | | Windows-GNU: Restore find_library treatment of '.dll' as linkable (#15409)Brad King2015-06-081-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Revert commit v3.3.0-rc1~435^2 (Windows-GNU: Do not tell find_library to treat '.dll' as linkable, 2015-02-18). MinGW tools support linking to '.dll' files directly and many non-CMake build systems still do not provide a separate '.dll.a' file.
* | | | Merge topic 'doc-add_custom_command-clarify-TARGET_FILE'Brad King2015-06-081-0/+3
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 0e708d17 Help: Reference TARGET_FILE genex in add_custom_command docs (#15605)
| * | | | Help: Reference TARGET_FILE genex in add_custom_command docs (#15605)Brad King2015-06-081-0/+3
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | Merge topic 'ExternalProject_init_selected_submodules'Brad King2015-06-081-0/+7
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 77ee6db5 Help: Add notes for topic 'ExternalProject_init_selected_submodules' 124243c0 ExternalProject: Add unit tests for GIT_SUBMODULES argument 14e2c3ad ExternalProject: Initialize only selected git submodules (#15590)
| * | | | Help: Add notes for topic 'ExternalProject_init_selected_submodules'Brad King2015-06-081-0/+7
| | |_|/ | |/| |
* | | | Remove CMAKE_USE_RELATIVE_PATHS variable.Stephen Kelly2015-06-032-7/+7
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test for this variable was removed in commit v2.8.8~330^2~7 (complex: Remove ancient unused ComplexRelativePaths test, 2011-12-23). Commit v3.1.0-rc1~425^2~2 (backtrace: Convert to local paths in IssueMessage, 2014-03-12) appears to have accidentally made some backtraces print relative paths with the variable because conversions which used to be done at configure time, before the variable had an effect are now potentially done at generate time. The documentation of the variable says not to use it, and the docs are wrong in that the variable actually applies in per-directory scope. The read of the variable makes it harder to split conversion methods from cmLocalGenerator where they don't belong. Remove it now.
* | | Begin post-3.3 developmentBrad King2015-06-022-0/+9
| |/ |/|
* | Help: Drop development topic notes to prepare releaseBrad King2015-06-022-9/+0
|/ | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* Help: Organize and revise 3.3 release notesBrad King2015-06-021-139/+169
| | | | | | Add section headers similar to the 3.2 release notes and move each individual bullet into an appropriate section. Revise and consolidate some bullets covering related areas.
* Help: Consolidate 3.3 release notesBrad King2015-06-0256-363/+264
| | | | | | | | | | | | | | Move all development release notes into a new version-specific document: tail -q -n +3 Help/release/dev/* > Help/release/3.3.rst git rm -- Help/release/dev/* except the sample topic: git checkout HEAD -- Help/release/dev/0-sample-topic.rst Reference the new document from the release notes index document. Add a title and intro sentence to the new document by hand.
* Merge topic 'doc-add_dependencies-no-install'Brad King2015-06-011-1/+2
|\ | | | | | | | | 9504d7a9 Help: Explicitly mention lack of 'install' support in add_dependencies
| * Help: Explicitly mention lack of 'install' support in add_dependenciesBrad King2015-06-011-1/+2
| | | | | | | | | | | | CMake-generated targets are not supported by add_dependencies. State this explicitly and use 'install' as an example since this may be commonly attempted.
* | Help: Fix typo in cmake-compile-features(7) manual (#15594)Erik Sjölund2015-05-291-1/+1
|/ | | | | | | target_link_libraries() is being used in the example code but target_include_directories() was probably meant to be used. The sentence that starts with "Consuming code then" indicates that the example is about using the appropriate include directory.
* Merge topic 'extend-visibility-properties'Brad King2015-05-267-21/+54
|\ | | | | | | | | | | | | | | 700f1c3b Honor visibility properties for all target types (#15556) 50de5dbb Help: Format visibility property and variable documentation 771f1b00 Tests: Rename Visibility{InlinesHidden =>} ab55b3b5 Tests: Refactor RunCMake.VisibilityPreset test setup
| * Honor visibility properties for all target types (#15556)Brad King2015-05-265-4/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The <LANG>_VISIBILITY_PRESET and VISIBILITY_INLINES_HIDDEN were first merged in commit v2.8.12~322 (Merge topic 'VISIBILITY_PRESET-property', 2013-06-05) but worked only for shared libraries and executables with exports. Prior to commit v3.0.0-rc1~581^2 (GenerateExportHeader: Deprecate add_compiler_export_flags function., 2013-09-02) the add_compiler_export_flags function was used to add visibility flags to all targets. The visibility flags are useful for sources in all target types because they may be later linked into shared libraries or executables with exports. Introduce policy CMP0063 to enable them for all target types while preserving compatibility with existing projects that do not expect this.
| * Help: Format visibility property and variable documentationBrad King2015-05-224-18/+13
| | | | | | | | Add reStructuredText markup appropriately.
* | Merge topic 'ExternalData-no-symlinks'Brad King2015-05-261-0/+7
|\ \ | |/ |/| | | | | 0de47b05 ExternalData: Add option to disable use of symlinks
| * ExternalData: Add option to disable use of symlinksBrad King2015-05-221-0/+7
| | | | | | | | | | | | | | | | | | Add an ExternalData_NO_SYMLINKS to enable use of copies instead of symlinks to populate the real data files behind a DATA{} reference. This will be useful on UNIX-like systems when the underlying filesystem does not actually support symbolic links. Suggested-by: Matt McCormick <matt.mccormick@kitware.com>
generated by cgit v0.12 at 2025-01-22 02:52:31 (GMT)