summaryrefslogtreecommitdiffstats
path: root/Help/release/dev
Commit message (Collapse)AuthorAgeFilesLines
* Help: Drop development topic notes to prepare releaseBrad King2020-06-051-7/+0
| | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* Help: Consolidate 3.18 release notesBrad King2020-06-0360-370/+0
| | | | | Run the `Utilities/Release/consolidate-relnotes.bash` script to move notes from `Help/release/dev/*` into `Help/release/3.18.rst`.
* add_library/add_executable: allow local alias to imported targetsMarc Chevrier2020-06-021-0/+6
| | | | Fixes: #20641
* Merge topic 'target_link_libraries-self-link-is-an-error'Brad King2020-06-021-0/+5
|\ | | | | | | | | | | | | 9436ad35df target_link_libraries: self-link through ALIAS is an error Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4826
| * target_link_libraries: self-link through ALIAS is an errorMarc Chevrier2020-05-301-0/+5
| | | | | | | | Fixes: #19617
* | ExternalProject: Add missing release note for git update strategyCraig Scott2020-05-291-0/+9
|/ | | | This release note was mistakenly omitted from commit 0aea435aa1 (ExternalProject: Provide choice of git update strategies, 2020-02-12).
* ALIAS target: cannot overwrite an existing targetMarc Chevrier2020-05-281-0/+5
| | | | Fixes: #19616
* CheckLinkerFlag: Add module to check validity of linker flagsMarc Chevrier2020-05-251-0/+5
| | | | Fixes: #15934
* Merge topic 'fortran-preprocess-property'Brad King2020-05-221-0/+6
|\ | | | | | | | | | | | | | | | | | | 3888de23da Ninja: Skip Fortran preprocessing if Fortran_PREPROCESS is OFF 66c4e87282 Ninja: Add helper functions to generate Fortran build 5cca1ec893 Ninja: Add helper functions to generate Fortran preprocess rule b0a6161190 Fortran: Add Fortran_PREPROCESS property Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4659
| * Fortran: Add Fortran_PREPROCESS propertyPeter Hill2020-05-211-0/+6
| | | | | | | | Issue: #18870
* | Merge topic 'cmake_language-rename-from-cmake_command'Craig Scott2020-05-222-6/+6
|\ \ | | | | | | | | | | | | | | | | | | 94c1e4fdb3 cmake_language: Rename command from cmake_command Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4774
| * | cmake_language: Rename command from cmake_commandBrad King2020-05-212-6/+6
| | | | | | | | | | | | | | | | | | Also rename the `INVOKE` signature to `CALL`. Fixes: #20732
* | | Merge topic 'multi-ninja-pch-msvc'Brad King2020-05-211-0/+4
|\ \ \ | |/ / |/| | | | | | | | | | | | | | f6cb1e646c Multi-Ninja: Fix PCHs for Visual C++ Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4771
| * | Multi-Ninja: Fix PCHs for Visual C++Cristian Adam2020-05-201-0/+4
| | | | | | | | | | | | Fixes: #20711
* | | Merge topic 'ctest-log-environment'Brad King2020-05-201-0/+8
|\ \ \ | |/ / |/| | | | | | | | | | | | | | a1612af749 CTest: Log environment variables as a test measurement Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4760
| * | CTest: Log environment variables as a test measurementKyle Edwards2020-05-191-0/+8
| | |
* | | Merge topic 'fetchcontent-SOURCE_SUBDIR'Brad King2020-05-181-0/+6
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 592085b94b FetchContent: Add support for SOURCE_SUBDIR Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4757
| * | | FetchContent: Add support for SOURCE_SUBDIRCraig Scott2020-05-161-0/+6
| |/ / | | | | | | Fixes: #19875
* | | CUDA: Add support for Clang compilerRaul Tambre2020-05-151-0/+4
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When crosscompiling we pass the sysroot. We need to try various architecture flags. Clang doesn't automatically select one that works. First try the ones that are more likely to work for modern installations: * <=sm_50 is deprecated since CUDA 10.2, try sm_52 first for future compatibility. * <=sm_20 is removed since CUDA 9.0, try sm_30. Otherwise fallback to Clang's current default. Currently that's `sm_20`, the lowest it supports. Separable compilation isn't supported yet. Fixes: #16586
* | Merge topic 'source_file_scopes'Brad King2020-05-151-0/+15
|\ \ | | | | | | | | | | | | | | | | | | 3d4b70ea64 set_source_files_properties: Allow specification of directory scope Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4661
| * | set_source_files_properties: Allow specification of directory scopeAlexandru Croitor2020-05-141-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Both set_source_files_properties() and set_property(SOURCE) now accept two new optional arguments: DIRECTORY and TARGET_DIRECTORY. The DIRECTORY option takes a list of relative or absolute paths pointing to processed source directories (add_subdirectory was already called on them). These paths specify directory scopes where the source file properties will be set. Previously the scope was always the currently processed source directory. Similarly TARGET_DIRECTORY takes a list of targets, whose source directories will be used as the list of scopes where to set the source file properties. get_property() and get_source_file_property() also get the same new arguments, except only one value can be specified instead of a list. Fixes: #20128
* | | Merge topic 'FindPython-IronPython-support'Brad King2020-05-131-0/+5
|\ \ \ | |/ / |/| | | | | | | | | | | | | | e8ffc60220 FindPython: Add IronPython support on all platforms Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4730
| * | FindPython: Add IronPython support on all platformsMarc Chevrier2020-05-111-0/+5
| |/
* | Merge topic 'source_group_forward_slashes'Brad King2020-05-111-0/+5
|\ \ | | | | | | | | | | | | | | | | | | faf44a8cdb source_group: Support forward slashes in group hierarchy Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4727
| * | source_group: Support forward slashes in group hierarchyCraig Scott2020-05-101-0/+5
| |/ | | | | Fixes: #18076
* | Unity Builds: Support explicit specification of sources to groupsRobert Maynard2020-05-071-0/+6
|/ | | | | Instead of having CMake determine which files should go into each unity file, the user can now use explicitly state the mapping.
* FindPython: Add support for 'PyPy'Marc Chevrier2020-05-011-0/+5
|
* Merge topic 'FPHSA-handle-components'Brad King2020-05-011-0/+5
|\ | | | | | | | | | | | | 0b6332af60 FPHSA: REQUIRED_VARS is optional if HANDLE_COMPONENTS is specified Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4690
| * FPHSA: REQUIRED_VARS is optional if HANDLE_COMPONENTS is specifiedMarc Chevrier2020-04-301-0/+5
| | | | | | | | Fixes: #20655
* | Merge topic 'CTestCoverageCollectGCOV-compress-opts'Brad King2020-05-011-0/+7
|\ \ | |/ |/| | | | | | | | | | | | | 40ca6ef125 CTestCoverageCollectGCOV: Add TARBALL_COMPRESSION option 81e83510a0 Tests: Fix re-running CTestCoverageCollectGCOV on in-source build ab7eda2591 Tests: Remove unnecessary pass regex on CTestCoverageCollectGCOV Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4649
| * CTestCoverageCollectGCOV: Add TARBALL_COMPRESSION optionKelly (KT) Thompson2020-04-301-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | For large projects, the default bzip2 compression of gcov data is prohibitively expensively (could take several hours). Introduce options that allow the consumer to choose between file size and compression time. Add a new optional argument `TARBALL_COMPRESSION` for the macro `ctest_coverage_collect_gcov`. This option accepts the values `GZIP`, `BZIP2`, `XZ`, `FROM_EXT`, or an expression that evaluates to `FALSE`. The default value is `BZIP2` to preserve prior behavior. Fixes: #20593
* | Merge topic 'vs_platform_toolset'Brad King2020-04-291-0/+6
|\ \ | | | | | | | | | | | | | | | | | | 197b4cbe18 VS: Add option for per-target PlatformToolset Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4682
| * | VS: Add option for per-target PlatformToolsetJulien Jemine2020-04-291-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | Add a `VS_PLATFORM_TOOLSET` target property to set `PlatformToolset` in the `.vcxproj` file for specific targets. Document that this is safe only when the named toolset uses the same underlying compiler as the primary toolset. Fixes: #17429
* | | Merge topic 'FindLibXslt-targets'Brad King2020-04-291-0/+4
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8a90ef5a44 FindLibXslt: use LIBXSLT_LIBRARY as cache variable 1aa7df4114 FindLibXslt: provide imported targets dd506714f4 FindLibXslt: identify libexslt include directory Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4650
| * | | FindLibXslt: provide imported targetsMarkus Rickert2020-04-281-0/+4
| | |/ | |/|
* | | Merge topic 'FindPython-find-implementations'Brad King2020-04-291-0/+5
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | d2c47c822b FindPython: Add capability to specify Python implementations Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4676
| * | FindPython: Add capability to specify Python implementationsMarc Chevrier2020-04-281-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | Through hint Python_FIND_IMPLEMENTATIONS it is possble to specify, as an ordered list, which implementations must be searched for. Currently possible values are: * CPython * IronPython
* | | FindLAPACK: Provide the LAPACK::LAPACK import targetRobert Maynard2020-04-271-0/+4
|/ /
* | Merge topic 'ccmake-custom-colors'Brad King2020-04-271-0/+5
|\ \ | | | | | | | | | | | | | | | | | | | | | 671fe28313 ccmake: Improve coloring, allow customization f56a695440 ccmake: Rename cmCursesColor::{Options => Choice} Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4629
| * | ccmake: Improve coloring, allow customizationMatthew Woehlke2020-04-241-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change the default color for strings from BLUE (which is nearly illegible on any terminals using the standard color palette which has been around since at least CGA, almost 40 years ago) to CYAN. Add ability to customize the colors via an environment variable (inspired by LS_COLORS and using similar syntax). Fixes: #20596
* | | Merge topic 'FindBLAS-target'Brad King2020-04-271-0/+4
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 85a9813a76 BLAS: Provide the BLAS::BLAS import target Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4657
| * | | BLAS: Provide the BLAS::BLAS import targetRobert Maynard2020-04-231-0/+4
| | | |
* | | | Merge topic 'remove-documentation-module'Brad King2020-04-231-0/+6
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 306a1ba960 Modules/Documentation: remove ad4487a96a cmIncludeCommand: add infrastructure for deprecated modules Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4617
| * | | | Modules/Documentation: removeBen Boeckel2020-04-221-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an old module from when VTK and other Kitware projects drove the addition of commands and modules into CMake itself. Modern VTK doesn't need this module and it can be ignored. This module is kept around so that the ancient VTK versions which use it are not broken by it. VTK itself stopped using the module in 2012 and the last usage by an example in VTK was removed in 2020. Fixes: #20591
* | | | | Merge topic 'ninja-compiler-PATH-windows'Brad King2020-04-231-0/+7
|\ \ \ \ \ | |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | e01990999a Ninja: On Windows, select the compiler occurring first in PATH Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4625
| * | | | Ninja: On Windows, select the compiler occurring first in PATHBrad King2020-04-221-0/+7
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Windows, toolchains like MSVC require a set of environment variables to be configured for the compiler to work correctly. The scripts that prepare these environments typically put the compiler's directory ahead of others in the `PATH`. Teach the Ninja generators to use this as a heuristic to select the compiler when none is explicitly specified. This is not necessary with Makefile generators because each toolchain's environment comes with its own make tool variant, and the corresponding Makefile generator (e.g. "NMake Makefiles") automatically implies the matching compiler. Fixes: #20585
* | | | Merge topic 'ctest_stop_on_failure_16628'Brad King2020-04-221-0/+8
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | e89aeba5c4 ctest: add option --stop-on-failure Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4630
| * | | ctest: add option --stop-on-failureJohnny Jazeix2020-04-201-0/+8
| |/ / | | | | | | | | | | | | | | | To stop the tests once one has failed Fixes: #16628
* | | CUDA: Device linking use now link optionsMarc Chevrier2020-04-191-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | properties LINK_OPTIONS and INTERFACE_LINK_OPTIONS are propagated to the device link step. To control which options are selected for normal link and device link steps, the $<DEVICE_LINK> and $<HOST_LINK> generator expressions can be used. Fixes: #18265
* | | Genex: Add generator expressions $<DEVICE_LINK> and $<HOST_LINK>Marc Chevrier2020-04-191-0/+6
|/ / | | | | | | | | | | These generator expressions can only be used in link options properties. These expressions return the arguments respectively for device and host link step, otherwise return an empty string.
generated by cgit v0.12 at 2025-01-06 07:55:33 (GMT)