summaryrefslogtreecommitdiffstats
path: root/Modules
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'cpack-generator-documentation'Brad King2018-06-2216-3387/+453
|\ | | | | | | | | | | | | | | | | | | | | | | 57e4c51e8a Help: Update old version release notes for CPack generator docs 4181830881 Help: Add release notes for CPack generator documentation and module updates 48bc8b2b82 CPack: Move internal implementation modules into Internal/CPack directory 2a2829cc75 Help: Add new section for CPack generators be6267808a CPackIFW: Turn documentation into a block comment 0180524c7a Help: Move legacy CPack modules into separate section Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2149
| * CPack: Move internal implementation modules into Internal/CPack directoryKyle Edwards2018-06-2116-2716/+136
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These modules are not meant to be included by user code, they are only an internal implementation detail for CPack. Having them live in the main Modules directory with documentation was misleading, so they have been moved into Modules/Internal/CPack, and their documentation has been stripped following its move into the new "CPack Generators" section. No-op modules which contained only documentation have been removed entirely. The only module that hasn't been moved is CPackIFW, because it contains user-facing macros which would be lost if it were moved. So, the CPackIFW module has been updated with a note explaining what needs to (eventually) happen.
| * Help: Add new section for CPack generatorsKyle Edwards2018-06-211-358/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The documentation for CPack generators previously lived in their respective internal CMake modules. This setup was misleading, because it implied that you should include the modules in your own code, which is not the case. Moving the documentation into a separate section does a better job of hiding the internal modules, which are just an implementation detail. The generator documentation has also been modified to remove any references to the module name. The CPackIFW module is a special exception: since it has user-facing macros, the documentation for these macros has been kept in the module page, while all other documentation related to the IFW generator has been moved into the new section. To make it easier to find the new documentation, the old help pages for the CPack*.cmake modules have not been deleted, but have been replaced with a link to their respective help page in the new documentation section.
| * CPackIFW: Turn documentation into a block commentKyle Edwards2018-06-211-671/+672
| |
* | Merge topic 'FindJPEG-fix-debug'Brad King2018-06-221-7/+1
|\ \ | |/ |/| | | | | | | | | | | ae4a548302 FindJPEG: Drop ancient compatibility NATIVE_JPEG_* result variables 7876f329a9 FindJPEG: Add forgotten names of libraries for Debug configuration Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2159
| * FindJPEG: Drop ancient compatibility NATIVE_JPEG_* result variablesAndrey Karpov2018-06-211-6/+0
| | | | | | | | These have been deprecated since 2002!
| * FindJPEG: Add forgotten names of libraries for Debug configurationAndrey Karpov2018-06-211-1/+1
| | | | | | | | | | | | The change in commit v3.12.0-rc1~202^2~1 (FindJPEG: Add multi config support and associated docs, 2018-04-17) accidentally left out the default jpeg library names from consideration for debug variants.
* | Merge topic 'xcode-10-archs'Brad King2018-06-196-12/+14
|\ \ | | | | | | | | | | | | | | | | | | bc5bcad45e Xcode: Detect architecture(s) using ARCHS instead of CURRENT_ARCH Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2153
| * | Xcode: Detect architecture(s) using ARCHS instead of CURRENT_ARCHBrad King2018-06-186-12/+14
| |/ | | | | | | | | | | | | | | | | Xcode 10 no longer populates `CURRENT_ARCH` with the current architecture in shell scripts and instead uses `undefined_arch`. Instead we must use `ARCHS`. It lists all architectures separated by spaces. Fixes: #18085
* | Merge topic 'FindCURL-target-name'Brad King2018-06-191-5/+5
|\ \ | | | | | | | | | | | | | | | | | | | | | 1e356734a7 FindCURL: Rename imported target to match upstream CURL Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Rolf Eike Beer <eike@sf-mail.de> Merge-request: !2154
| * | FindCURL: Rename imported target to match upstream CURLBrad King2018-06-181-5/+5
| |/ | | | | | | | | | | | | | | | | | | | | Upstream CURL provides imported target `CURL::libcurl`. Rename the target added by `FindCURL` to match. We don't need compatibility with the old name because it has never been in a CMake release (except a 3.12 release candidate). Suggested-by: Jakub Zakrzewski <slither.jz@gmail.com> Acked-by: Rolf Eike Beer <eike@sf-mail.de> Fixes: #18091
| * Merge branch 'UseSWIG-csharp-variant' into release-3.12Brad King2018-06-131-2/+7
| |\ | | | | | | | | | Merge-request: !2137
| * \ Merge branch 'UseSWIG-fix-genex' into release-3.12Brad King2018-06-121-7/+7
| |\ \ | | | | | | | | | | | | Merge-request: !2143
| * \ \ Merge branch 'UseSWIG-handle-SWIG_MODULE_NAME' into release-3.12Brad King2018-06-121-1/+1
| |\ \ \ | | | | | | | | | | | | | | | Merge-request: !2145
| * \ \ \ Merge branch 'FindPython-3.8' into release-3.12Brad King2018-06-083-3/+3
| |\ \ \ \ | | | | | | | | | | | | | | | | | | Merge-request: !2140
* | | | | | UseSWIG: add support of target property INCLUDE_DIRECTORIES consumptionMarc Chevrier2018-06-131-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | Fixes: #18003
* | | | | | Merge topic 'UseSWIG-csharp-variant'Brad King2018-06-131-2/+7
|\ \ \ \ \ \ | | |_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | 0c2fb4c896 UseSWIG: Add CSHARP variant for wrapper files Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2137
| * | | | | UseSWIG: Add CSHARP variant for wrapper filesRishi Theivendran2018-06-121-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Issue: #18065 Fixes: #18066
* | | | | | Merge topic 'UseSWIG-fix-genex'Brad King2018-06-131-7/+7
|\ \ \ \ \ \ | | |_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | 88dd5dc9ff UseSWIG: add support for generator expressions Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2143
| * | | | | UseSWIG: add support for generator expressionsMarc Chevrier2018-06-121-7/+7
| |/ / / /
* | | | | Merge topic 'UseSWIG-handle-SWIG_MODULE_NAME'Brad King2018-06-131-1/+1
|\ \ \ \ \ | | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | 156138d5f1 UseSWIG: Fix handling of `SWIG_MODULE_NAME` source file property Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2145
| * | | | UseSWIG: Fix handling of `SWIG_MODULE_NAME` source file propertyFelix Schwitzer2018-06-121-1/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix a typo from commit 0bef9eb410 (UseSWIG: modernize module, 2018-01-29) that caused `UseSWIG` to ignore an eventually set property `SWIG_MODLUE_NAME`. Building multiple python modules using the mentioned property as described in the docs could lead to an invalid, or even worse, inconsistent `build.ninja` file. The reason is that the generated list of support files was not unique. For each module the support file was always named the same, namely `path/to/builddir/MODULENAME.py`.
* | | | Merge topic 'FindPython-3.8'Brad King2018-06-123-3/+3
|\ \ \ \ | | |_|/ | |/| | | | | | | | | | | | | | | | | | b6e7f2c37f FindPython: Add support for version 3.8 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2140
| * | | FindPython: Add support for version 3.8Marcel Plch2018-06-083-3/+3
| |/ / | | | | | | | | | Python 3.7 is about to be released, making the development version 3.8.
* | | Merge topic 'LINK_OPTIONS'Brad King2018-06-0823-3/+61
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | 66ea1a3795 LINK_OPTIONS: Add support of "LINKER:" prefix c1f5a44b28 LINK_OPTIONS: Add new family of properties 8e28d2630a Makefile generator: link flags management refactoring Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Alex Turbov <i.zaufi@gmail.com> Merge-request: !2033
| * | LINK_OPTIONS: Add support of "LINKER:" prefixMarc Chevrier2018-06-0623-3/+61
| |/
* | Help: Package without components should use 'check_required_components' tooRuslan Baratov2018-06-071-7/+9
|/ | | | | | | | | Macro 'check_required_components' should be called even if there are no components provided by package. This will make sure error is reported in next cases: find_package(Foo CONFIG REQUIRED oops) # 'oops' treated as component find_package(Foo CONFIG REQUIRED COMPONENTS foo) # no components expected
* Merge topic 'intel-compile-features'Brad King2018-06-051-1/+1
|\ | | | | | | | | | | | | f719a13c28 Features: Add special case to disable relaxed constexpr for Intel 18 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2133
| * Features: Add special case to disable relaxed constexpr for Intel 18Brad King2018-06-041-1/+1
| | | | | | | | | | | | | | | | | | | | Intel compilers define `__cpp_constexpr` to `200704` even in C++14 mode. This indicates that the `cxx_relaxed_constexpr` feature is not available. However, Intel 17 and above document support for it. In commit v3.8.0~9^2 (Features: Update features for Intel C++ 17.0.2 on UNIX, 2017-03-31) we added a special check for this case. Intel 17 and 19 work. However, Intel 18 does not seem to work and fails our test case. Add a special case to disable the feature for Intel 18.
* | Merge topic 'more-misc-typos'Brad King2018-06-056-11/+11
|\ \ | | | | | | | | | | | | | | | | | | | | | be28106880 Fix misc. typos Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Alex Turbov <i.zaufi@gmail.com> Merge-request: !2130
| * | Fix misc. typosluz.paz2018-06-046-11/+11
| | | | | | | | | | | | Found via `codespell` and `grep`
* | | Merge topic 'ep-support-passing-var-ending-with-notfound'Brad King2018-06-051-1/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 7ad5165c67 ExternalProject: Fix cache generation when args end with "-NOTFOUND" Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2127
| * | | ExternalProject: Fix cache generation when args end with "-NOTFOUND"Jean-Christophe Fillion-Robin2018-06-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Generalize the fix in commit v3.11.0-rc4~8^2 (ExternalProject: Fix cache generation when last args ends with "-NOTFOUND", 2018-03-10) to work for any argument rather than just the last one. ExternalProject can now successfully generate the cache file when any (not only the last one) cache variable associated with either `CMAKE_CACHE_ARGS` or `CMAKE_DEFAULT_CACHE_ARGS` configure step option is set to a `<value>` ending with `-NOTFOUND`.
* | | | Merge topic 'fix/CPackNuGet-var-para-deindent'Craig Scott2018-06-051-2/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | afcb68a0c1 Help: Fix indentation for `CPACK_NUGET_PACKAGE_AUTHORS` Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2135
| * | | | Help: Fix indentation for `CPACK_NUGET_PACKAGE_AUTHORS`Alex Turbov2018-06-051-2/+2
| | | | |
* | | | | Merge topic 'external-project-url-hash-docs'Craig Scott2018-06-051-3/+3
|\ \ \ \ \ | |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | 470ff56e5a ExternalProject: Improve URL_HASH argument description Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2134
| * | | | ExternalProject: Improve URL_HASH argument descriptionMatt McCormick2018-06-041-3/+3
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | The previous documentation suggested ALGO=MD5=d7a3dc7757a35df3dbb890f7dee0976b for example.
* | | | Merge topic 'fix-ti-c-standard'Brad King2018-06-041-0/+6
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 9e27881bb1 TI: Add support for C language standards Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2131
| * | | | TI: Add support for C language standardsArnaud Gelas2018-06-041-0/+6
| | |_|/ | |/| | | | | | | | | | | | | | | | | | Set C90 and C99 compile options for TI compiler. Fixes: #18061
* | | | Merge topic 'gnu-CMAKE_LANG_COMPILER_PREDEFINES_COMMAND'Brad King2018-06-042-1/+2
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | caa138c1a5 Move GNU COMPILER_PREDEFINES_COMMAND from Platform to Compiler Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2121
| * | | Move GNU COMPILER_PREDEFINES_COMMAND from Platform to CompilerSebastian Holtermann2018-06-012-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Moves `CMAKE_${lang}_COMPILER_PREDEFINES_COMMAND` from linux specific [Modules/Platform/Linux-GNU.cmake](Modules/Platform/Linux-GNU.cmake) to [Modules/Compiler/GNU.cmake](Modules/Compiler/GNU.cmake). This enables compiler predefines generation (in AUTOMOC) on all platforms that run gcc (and clang).
* | | | Revise C++ coding style using clang-format-6.0Kitware Robot2018-06-018-29/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Run the `clang-format.bash` script to update all our C and C++ code to a new style defined by `.clang-format`. Use `clang-format` version 6.0. * If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content. * See the parent commit for instructions to rebase a change across this style transition commit.
* | | | clang-format: Add comments to suppress some formattingBrad King2018-06-011-1/+2
| | | | | | | | | | | | | | | | Preserve manually-formatted blocks.
* | | | FindALSA: reformat docsRolf Eike Beer2018-05-311-9/+16
| | | |
* | | | FindALSA: provide an imported targetRolf Eike Beer2018-05-311-0/+14
|/ / /
* | | Merge topic 'vs-toolset-version'Brad King2018-05-302-0/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5f13168419 VS: Add option to select the version of the toolset used by VS 2017 Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Francisco Facioni <fran6co@gmail.com> Merge-request: !2093
| * | | VS: Add option to select the version of the toolset used by VS 2017Basil Fierz2018-05-292-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add new `version=` parameter in the toolset setting to select the version. Add variable `CMAKE_VS_PLATFORM_TOOLSET_VERSION` to hold the version, if one is set (blank indicates default). Fixes: #17549
* | | | Merge topic 'cuda-unused-placeholder'Brad King2018-05-292-7/+7
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | edf0ea9bb2 CUDA: Drop unused/broken platform link flags placeholder Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2108
| * | | CUDA: Drop unused/broken platform link flags placeholderBrad King2018-05-252-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `<CMAKE_CUDA_LINK_FLAGS>` placeholder in CUDA rule variables comes from the `<CMAKE_CXX_LINK_FLAGS>` placeholder from which the CUDA rule variables were originally derived. It is not a public interface for adding link flags so no projects should be using it. It is needed for platform information modules to specify platform-specific link flags for the language. None of our platform modules set it, so it is unused. Furthermore, it is broken as currently implemented. Some of the contexts in which it is used need `-Xlinker` and some do not. Therefore it is not possible to use the placeholder at all. Simply remove it for now. If some need for platform-specific CUDA link flags arises a new solution will be needed.
* | | | Merge topic 'doxygen-all'Craig Scott2018-05-291-2/+10
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 7b2f440e2b FindDoxygen: Add tests for ALL option 79b29b732c FindDoxygen: add optional ALL argument Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2099
generated by cgit v0.12 at 2025-01-01 11:54:17 (GMT)