summaryrefslogtreecommitdiffstats
path: root/Help/release
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'extend-visibility-properties'Brad King2015-05-261-0/+7
|\ | | | | | | | | | | | | | | 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-261-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | 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>
* | Revert "Qbs: Add new 'extra' generator for qbs project files"Brad King2015-05-211-6/+0
|/ | | | | | | | | | | | | | | | | | | This reverts commit f85db2f32358e6de921aba7d1cb8ecb81da934c0. Discussion by the QtCreator community at https://bugreports.qt.io/browse/QTCREATORBUG-13695 raises concerns about this particular approach to working with CMake projects using QtCreator. Also, the functionality and design of the QBS extra generator was never discussed on the CMake mailing list or with QtCreator developers. There may be better ways to make the two tools work together. In order to avoid committing to long-term support of this generator prior to such discussion taking place, revert it from CMake for now. We may restore this or use an alternative design based on results of such discussion.
* Merge topic 'cmake-gui-osx-install-command-line'Brad King2015-05-211-0/+10
|\ | | | | | | | | | | | | | | 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
| * Help: Add notes for topic 'cmake-gui-osx-install-command-line'Brad King2015-05-211-0/+10
| |
* | Add options to run include-what-you-use with the compilerBrad King2015-05-191-0/+8
|/ | | | | | 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.
* Merge topic 'cpack-ifw-updates'Brad King2015-05-181-0/+5
|\ | | | | | | | | | | 342d15cb Update packaging of CMake for QtIFW 2.0 9a0ba4d2 CPackIFW: Add QtIFW 2.0 support
| * CPackIFW: Add QtIFW 2.0 supportKonstantin Podsvirov2015-05-151-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | install: Disallow installing export() result.Stephen Kelly2015-05-141-0/+5
|/
* Merge topic 'ctest-no-make-i'Brad King2015-05-121-0/+7
|\ | | | | | | | | | | | | 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-121-0/+7
| | | | | | | | Add policy CMP0061 to maintain compatibility for existing projects.
* | 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-121-0/+10
|\ \ | |/ |/| | | | | | | 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-081-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | execute_process: Improve stdout/stderr mergingBrad King2015-05-071-0/+5
|/ | | | | | | 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 'vs-install-in-default-build'Brad King2015-05-071-0/+7
|\ | | | | | | | | | | 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-061-0/+7
| | | | | | | | | | 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
* if: Implement new IN_LIST operatorNils Gladitz2015-04-301-0/+5
|
* Revert "add_custom_command: Diagnose MAIN_DEPENDENCY limitation."Nils Gladitz2015-04-301-6/+0
| | | | | | | | | | | | 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.
* Help: Add notes for topic 'ExternalProject-genex'Brad King2015-04-211-0/+6
|
* 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-201-0/+8
|\ \ | |/ |/| | | | | | | | | 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
| |
* | 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.
* | | Deprecate Visual Studio 7 generator (.NET 2002)Brad King2015-04-151-0/+5
| | | | | | | | | | | | | | | Update documentation to mark the generator deprecated. Add a warning at the end of generation plus an option to turn off the warning.
* | | Deprecate Visual Studio 6 generatorBrad King2015-04-151-0/+5
|/ / | | | | | | | | Update documentation to mark the generator deprecated. Add a warning at the end of generation plus an option to turn off the warning.
* | cmake: Teach "-E tar" command a "--format=" optionNils Gladitz2015-04-101-0/+6
| | | | | | | | | | | | | | Allows specifying a libarchive defined archive format currently restricted to 7zip, gnutar, pax, paxr and zip. The default is "paxr" (pax restricted).
* | Merge topic 'link-implicit-libs-full-path'Brad King2015-04-091-0/+6
|\ \ | |/ |/| | | | | | | | | 882f48e5 Link libraries by full path even in implicit directories 318cd370 Help: Add link target for Find Modules section of cmake-developer.7 1535dcd8 Tests: Teach RunCMake to optionally merge command output to stdout
| * Link libraries by full path even in implicit directoriesBrad King2015-04-091-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When CMP0003 was first introduced we wanted to link all libraries by full path. However, some projects had problems on platforms where find_library would find /usr/lib/libfoo.so when the project really wanted to link to /usr/lib/<arch>/libfoo.so and had been working by accident because pre-CMP0003 behavior used -lfoo to link. We first tried to address that in commit v2.6.0~440 (Teach find_library to avoid returning library paths in system directories, 2008-01-23) by returning just "foo" for libraries in implicit link directories. This caused problems for projects expecting find_library to always return a full path. We ended up using the solution in commit v2.6.0~366 (... switch library paths found in implicit link directories to use -l, 2008-01-31). However, the special case for libraries in implicit link directories has also proven problematic and confusing. Introduce policy CMP0060 to switch to linking all libraries by full path even if they are in implicit link directories. Explain in the policy documentation the factors that led to the original approach and now to this approach.
* | Help: Add notes for topic 'emulator-property'Brad King2015-04-081-0/+7
| |
* | Merge topic 'gcov-module-coverage-exclude'Brad King2015-04-071-0/+6
|\ \ | |/ |/| | | | | d2240390 Help: Add notes for topic 'gcov-module-coverage-exclude'
| * Help: Add notes for topic 'gcov-module-coverage-exclude'Brad King2015-04-061-0/+6
| |
* | VS: Add support for XAML source filesGilles Khouzam2015-04-031-0/+6
| | | | | | | | | | | | | | | | XAML files are by default of type Page in the vcxproj and can be overriden by setting the VS_XAML_TYPE property. The .cpp and .h file of the same name are automatically added as depending on the XAML file. New VSXaml test builds a basic XAML WindowsStore 8.1 app with VS2013.
* | Merge topic 'FindCUDA.cmake/StaticRuntime'Brad King2015-04-031-0/+7
|\ \ | | | | | | | | | | | | 7fea2b77 FindCUDA: Use the static CUDA runtime library if available (#15482)
| * | FindCUDA: Use the static CUDA runtime library if available (#15482)James Bigler2015-04-031-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Beginning in CUDA 5.5 a static version of the cuda runtime library became available. Since nvcc defaults to using this library over the shared version, FindCUDA will also default to using this version. There are many advantages to using the static version (most importantly to avoid conflicts with multiple versions when building a CUDA based library). Offer a CUDA_USE_STATIC_CUDA_RUNTIME option to control this behavior.
* | | Do not treat DEFINITIONS as a built-in directory propertyStephen Kelly2015-04-021-0/+6
| |/ |/| | | | | | | | | | | | | Add policy CMP0059 to cover this change. The property has been deprecated since CMake 2.4 anyway. This will help clean up cmMakefile -- the DefineFlagsOrig member should not need to exist.
* | Merge topic 'makefile-DELETE_ON_ERROR'Brad King2015-04-011-0/+7
|\ \ | |/ |/| | | | | | | 44990732 Help: Add notes for topic 'makefile-DELETE_ON_ERROR' 4adf1dad Makefile: Tell GNU make to delete rule outputs on error (#15474)
| * Help: Add notes for topic 'makefile-DELETE_ON_ERROR'Brad King2015-03-311-0/+7
| |
* | Merge topic 'UseSWIG-no-MAIN_DEPENDENCY'Brad King2015-03-311-0/+9
|\ \ | | | | | | | | | | | | 1570a4df Help: Add notes for topic 'UseSWIG-no-MAIN_DEPENDENCY'
| * | Help: Add notes for topic 'UseSWIG-no-MAIN_DEPENDENCY'Brad King2015-03-311-0/+9
| |/
* | Help: Add notes for topic 'cpack-rpm-basic-symlink-handling'Brad King2015-03-311-0/+6
|/
* Merge topic 'add_dependencies-INTERFACE-libraries'Brad King2015-03-301-0/+7
|\ | | | | | | | | | | ac14cbf0 Allow add_dependencies() on INTERFACE libraries (#15414) 817d31db Help: Format add_dependencies documentation
generated by cgit v0.12 at 2025-03-05 20:23:48 (GMT)