summaryrefslogtreecommitdiffstats
path: root/Help
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'target_genex_dependency'Brad King2020-09-017-11/+114
|\ | | | | | | | | | | | | | | f14b390198 GenEx: Remove unneeded dependencies from target info queries Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Raul Tambre <raul@tambre.ee> Merge-request: !5127
| * GenEx: Remove unneeded dependencies from target info queriesRobert Maynard2020-09-017-11/+114
| | | | | | | | | | | | | | | | | | | | Only generate a graph dependency between a custom command and a target when the custom command queries for the file path of an artifact of the target. This makes generator expressions such as `TARGET_FILE_DIR` behave the same way as `TARGET_PROPERTY` which never generated a graph dependency.
* | Merge topic 'xcode-link-phase-all'Craig Scott2020-09-015-0/+70
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 525464ed2a Xcode: Use "Link Binary With Libraries" build phase in some cases dc0898205c Xcode: Add special case for file type extension map for .xcassets 7b3d8411a2 Xcode: Refactor build setting append code and attribute getter naming Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5036
| * | Xcode: Use "Link Binary With Libraries" build phase in some casesGusts Kaksis2020-08-315-0/+70
| |/ | | | | | | | | | | | | OBJECT and STATIC libraries (framework or non-framework) do not use this build phase. Not all items to be linked use this build phase either. Co-Authored-By: Craig Scott <craig.scott@crascit.com>
* | Merge topic 'cuda_host_compiler_fail'Brad King2020-09-011-0/+6
|\ \ | | | | | | | | | | | | | | | | | | | | | 01428c5560 CUDA: Fail fast if CMAKE_CUDA_ARCHITECTURES doesn't work during detection 9f81aa0f69 CUDA: Fail if compiler detection using the host compiler fails Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5155
| * | CUDA: Fail fast if CMAKE_CUDA_ARCHITECTURES doesn't work during detectionRaul Tambre2020-08-291-1/+2
| | | | | | | | | | | | | | | Also re-ordered the code to avoid testing flags for other compilers, since we know the vendor before full detection.
| * | CUDA: Fail if compiler detection using the host compiler failsRaul Tambre2020-08-291-0/+5
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If an user specified a host compiler we should fail if we are unable to perform compiler detection with it. Previously we would try without and likely succeed and continue. Then we'd fail during ABI detection and compiler testing since we'd still try to use it. This is particularly problematic when crosscompiling since we extract the host linker from the compiler detection link line. This would result in the wrong host linker being used and a linking error due to architecture mismatch during ABI detection where other necessary flags may already be present to make the host compiler work. See #21076 for an example. Fix this by adding CMAKE_<LANG>_COMPILER_ID_REQUIRE_SUCCESS to CMakeDetermineCompilerId, which throws a fatal error if executing the compiler results in a non-zero exit code. Fixes #21120.
* | Merge topic 'file_chmod'Brad King2020-09-012-0/+52
|\ \ | | | | | | | | | | | | | | | | | | | | | 7de60beddf file: Add CHMOD and CHMOD_RECURSE subcommands Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Marc Chevrier <marc.chevrier@gmail.com> Merge-request: !5122
| * | file: Add CHMOD and CHMOD_RECURSE subcommandsSibi Siddharthan2020-08-262-0/+52
| | | | | | | | | | | | | | | | | | Fixes: #21057 Signed-off-by: Sibi Siddharthan <sibisiddharthan.github@gmail.com>
* | | Merge topic 'ispc_lang_support'Brad King2020-09-0112-3/+84
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5ece12b7e4 gitlab-ci: add ISPC to the Fedora CI image 8976817d6d ISPC: Update help documentation to include ISPC 2368f46ba4 ISPC: Support building with the MSVC toolchain e783bf8aa6 ISPC: Support ISPC header generation byproducts and parallel builds 34cc6acc81 Add ISPC compiler support to CMake 419d70d490 Refactor some swift only logic to be re-used by other languages Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5065
| * | | ISPC: Update help documentation to include ISPCRobert Maynard2020-08-289-5/+62
| | | |
| * | | ISPC: Support ISPC header generation byproducts and parallel buildsRobert Maynard2020-08-284-0/+24
| | | |
* | | | Help: Reference CMAKE_CUDA_COMPILER_ID not CMAKE_CUDA_COMPILERRaul Tambre2020-08-291-6/+6
| |_|/ |/| | | | | | | | | | | We should refer to the compiler ID in the documentation to avoid users checking compiler executable names, since that seems fragile.
* | | Merge topic 'vs-win-sdk-custom-max'Brad King2020-08-265-0/+39
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | ba497111f6 VS: Add option for custom Win10 SDK version maximum Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5150
| * | VS: Add option for custom Win10 SDK version maximumjonathan molinatto2020-08-255-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 83ddc4d289 (VS: Do not select a Windows SDK too high for current VS version, 2017-08-07, v3.13.0-rc1~72^2~2) we enforce a maximum SDK version for the VS 2015 generator. The blog post linked in the original commit is no longer available, but it can be seen here: * https://web.archive.org/web/20190108032520/https://blogs.msdn.microsoft.com/chuckw/2018/10/02/windows-10-october-2018-update/ In particular, it states: > VS 2015 Users: The Windows 10 SDK (15063, 16299, 17134, 17763) > is officially only supported for VS 2017. However, in some circumstances a higher version can be used. Add a `CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM` to override the generator's default maximum SDK version. Fixes: #20633
* | | Merge topic 'osx_asm_architectures'Brad King2020-08-251-0/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 940fc62962 macOS: Respect OSX_ARCHITECTURES for ASM Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5152
| * | | macOS: Respect OSX_ARCHITECTURES for ASMRaul Tambre2020-08-221-0/+5
| |/ / | | | | | | | | | Fixes #20771.
* | | Merge topic 'win32-executable-genex'Brad King2020-08-252-0/+9
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 3ef0c40962 WIN32_EXECUTABLE: Add support for generator expressions Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5146
| * | | WIN32_EXECUTABLE: Add support for generator expressionsKyle Edwards2020-08-212-0/+9
| |/ /
* | | Merge topic 'file_generate_target'Brad King2020-08-252-1/+10
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 27a912193b file(GENERATE): Add TARGET argument Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5131
| * | | file(GENERATE): Add TARGET argumentRaul Tambre2020-08-202-1/+10
| |/ / | | | | | | | | | | | | | | | | | | Adds TARGET argument to file(GENERATE) to make resolving generator expressions requiring a target possible. Implements #21101, fixes #21074.
* | | Merge topic 'unk_imported_location'Brad King2020-08-253-0/+26
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 359c500a24 cmTarget: Raise error if imported target location is not set Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5113
| * | | cmTarget: Raise error if imported target location is not setRaul Tambre2020-08-213-0/+26
| |/ / | | | | | | | | | | | | | | | | | | | | | Previously we would synthesize <TARGET_NAME>-NOTFOUND as the location. This would then end up on the link line and cause build failures. Policy CMP0110 is added to control this behaviour. Fixes #19080, #19943.
* | | Merge topic 'msvc_static_assert'Brad King2020-08-251-3/+10
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 95bc11dbb4 MSVC: Record support for c_static_assert Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5148
| * | | MSVC: Record support for c_static_assertRaul Tambre2020-08-201-3/+10
| | | | | | | | | | | | | | | | Supported since MSVC 19.28.29115 (VS 16.8.0 Preview 1.0).
* | | | Help: Separate C++ compile feature by standardFrancisco Pombal2020-08-231-55/+87
| |/ / |/| | | | | | | | | | | | | | Additionally, mention that no fine-grained features are available for C++ 17 and beyond. Co-Authored-By: Craig Scott <craig.scott@crascit.com>
* | | Help/dev: Update CMake Review Process document to suggest 'git describe'Brad King2020-08-201-0/+1
| | | | | | | | | | | | | | | Using `git describe --contains` is the preferred way to reference a commit relative to a tag.
* | | Merge topic 'cpack-wix-custom-xmlns'Brad King2020-08-192-0/+13
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 267de3ba30 CPack/WiX: Add support for custom XML namespaces Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5132
| * | | CPack/WiX: Add support for custom XML namespacesFritz Elfert2020-08-182-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | Add a `CPACK_WIX_CUSTOM_XMLNS` option to specify these. Fixes: #21098
* | | | Merge topic 'buildsystem_documentation_update'Brad King2020-08-191-5/+15
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cfcb71c530 Help: Update cmake-buildsystem documentation Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5123
| * | | | Help: Update cmake-buildsystem documentationJoseph Snyder2020-08-181-5/+15
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add additional information to the cmake-buildsystem manual: * Add link to "Generator Expressions" in a place which demonstrates a generator expression without linking to what they are. * Update "diagnostic message" for "Compatible Interface Properties" to contain an example of the message sent. * Add information about the macOS FRAMEWORK_VERSION and how "A" is the conventional value to use.
* | | | Merge topic 'fotran_module_vs_docs'Brad King2020-08-181-0/+8
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | c5407b95f0 Help: Expand Fortran_MODULE_DIRECTORY documentation. Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5128
| * | | | Help: Expand Fortran_MODULE_DIRECTORY documentation.Petr Kmoch2020-08-171-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | Document how Visual Studio generators append per-configuration directory to path where Fortran modules are created.
* | | | | Merge topic 'add_test-special-chars-in-name'Brad King2020-08-174-3/+35
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a20987732b add_test: Allow special characters in test name (w/ policy CMP0110) Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5076
| * | | | | add_test: Allow special characters in test name (w/ policy CMP0110)Deniz Bahadir2020-08-124-3/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Restore the change from commit f84af8e270 (add_test: Allow special characters in test name, 2020-05-16, v3.18.0-rc1~142^2) that had to be reverted by commit f84af8e270 (add_test: Allow special characters in test name, 2020-05-16, v3.18.0-rc1~142^2) for compatibility. Add policy CMP0110 to make the change in a compatible way. Also, support even more characters than before by generating the test scripts using bracket arguments around the test names. Fixes: #19391 Signed-off-by: Deniz Bahadir <dbahadir@benocs.com>
* | | | | | Merge topic 'ios-combined-prune-archs'Brad King2020-08-171-0/+6
|\ \ \ \ \ \ | |_|_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5852b8867f CMakeIOSInstallCombined: Enforce disjoint architecture sets 79098d23eb Tests: Avoid warnings about unused arguments Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5111
| * | | | | CMakeIOSInstallCombined: Enforce disjoint architecture setsGregor Jasny2020-08-081-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Starting with Xcode 12 the arm64 architecture is supported as an iOS device as well as simulator architecture. But the fat macho file format does not distinguish by SDK, only by architecture. That makes lipo (rightfully) complain that it cannot add both architectures to a single file. To work around we make sure that both SDKs are built for a disjoint set of architectures. If an architecture is present for both SDKs we prefer the currently configured one. The log output has been extended to reflect that: ``` [iOS combined] Architectures (iphoneos): arm64 arm64e armv7 armv7s [iOS combined] Architectures (iphonesimulator): arm64 arm64e i386 x86_64 [iOS combined] Architectures (iphonesimulator) after pruning: i386 x86_64 ```
* | | | | | Help: Improve formatting for IMPLICIT_DEPENDS_INCLUDE_TRANSFORMJosef Angstenberger2020-08-131-5/+5
| | | | | |
* | | | | | Merge topic 'optimize-static-library-deps'Kyle Edwards2020-08-135-0/+51
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2e42651dff Add option to optimize link dependencies for static libraries Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5103
| * | | | | Add option to optimize link dependencies for static librariesKyle Edwards2020-08-125-0/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add an `OPTIMIZE_DEPENDENCIES` target property and supporting `CMAKE_OPTIMIZE_DEPENDENCIES` variable to optionally enable pruning and flattening of outgoing dependencies from static libraries. Since they do not actually link, they only depend on side effects of their dependencies. Therefore we can drop dependencies that contribute no side effects.
* | | | | | Merge topic 'msvc_c11'Brad King2020-08-121-0/+7
|\ \ \ \ \ \ | |/ / / / / |/| | | | / | | |_|_|/ | |/| | | | | | | | | | | | | f7347f28c7 MSVC: Record support for C11 and c_restrict Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5115
| * | | | MSVC: Record support for C11 and c_restrictRaul Tambre2020-08-111-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MSVC >=19.27 supports a C11 switch. The `c_restrict` feature has also been implemented. Fixes: #21069
* | | | | Merge topic 'automoc-path-prefix-off'Brad King2020-08-113-4/+11
|\ \ \ \ \ | |/ / / / | | | / / | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | 5b5be34811 Help: Add 3.18.2 release note about AUTOMOC_PATH_PREFIX default change db659e18bc Merge branch 'backport-3.17-automoc-path-prefix-off' e503fbe38a Merge branch 'backport-3.16-automoc-path-prefix-off' 4c33b305a0 Autogen: Turn off moc path prefix generation by default Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5105
| * | | Help: Add 3.18.2 release note about AUTOMOC_PATH_PREFIX default changeJoerg Bornemann2020-08-101-0/+8
| | | |
| * | | Merge branch 'backport-3.17-automoc-path-prefix-off'Brad King2020-08-102-4/+3
| |\ \ \
| | * \ \ Merge branch 'backport-3.16-automoc-path-prefix-off'Brad King2020-08-102-4/+3
| | |\ \ \
| | | * | | Autogen: Turn off moc path prefix generation by defaultJoerg Bornemann2020-08-102-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change the default value of `CMAKE_AUTOMOC_PATH_PREFIX` to `OFF` to restore compatibility with behavior of CMake 3.15 and below. C++ source files that are generated by Qt's meta object compiler (moc) include the header file that was passed as input argument to moc. This is usually a path relative to the source directory, for example #include "../../source/dir/myobject.h" That is problematic for reproducible builds as described in #18815. To cope with that, the target property AUTOMOC_PATH_PREFIX was introduced in CMake 3.16 by commit d018d27c10 (Autogen: Add moc path prefix generation (AUTOMOC_PATH_PREFIX), 2019-09-13, v3.16.0-rc1~94^2~4). The property is default-initialized from the variable `CMAKE_AUTOMOC_PATH_PREFIX`, which defaults to `ON`. If this property is ON, and myobject.h is located in an include directory of the target, moc-generated C++ files include the file without the "path prefix": #include "myobject.h" This behavior, however, can break projects that have equally named header files in different include directories. As "not breaking existing projects" trumps "have reproducible builds by default" we change the default of `CMAKE_AUTOMOC_PATH_PREFIX` to `OFF`. Also, it is now possible to pass `-DCMAKE_AUTOMOC_PATH_PREFIX=ON` on the CMake command line. Before, it was overridden in `CMakeGenericSystem`. Fixes: #20598 Issue: #18815
* | | | | | Merge topic 'build-interface-targets'Brad King2020-08-105-24/+66
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bafa9fe887 fileapi: Add INTERFACE libraries with SOURCES to codemodel-v2 4391913133 Add INTERFACE libraries to generated buildsystem if they have SOURCES afb998704e Remove filtering of allowed INTERFACE library properties e7edba2baf Makefiles: Use IsInBuildSystem in global generator target type checks Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5078
| * | | | | | fileapi: Add INTERFACE libraries with SOURCES to codemodel-v2Brad King2020-08-071-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | INTERFACE libraries with SOURCES now appear in the generated buildsystem, so include them in the codemodel output too. We do not need to bump the `codemodel-v2` object kind minor version because that was already done in post-3.18 development by commit 7d6861f367 (fileapi: Extend codemodel targets with language standard, 2020-06-18). Fixes: #18608
| * | | | | | Add INTERFACE libraries to generated buildsystem if they have SOURCESBrad King2020-08-074-10/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | INTERFACE libraries were created with the intention of collecting usage requirements for use by other targets via `target_link_libraries`. Therefore they were not allowed to have SOURCES and were not included in the generated buildsystem. In practice, this has become limiting: * Header-only libraries do have sources, they just do not compile. Developers should be able to edit those sources (the header files) in their IDE. * Header-only libraries may need to generate some of their header files via custom commands. Some projects work around these limitations by pairing each interface library with an `add_custom_target` that makes the header files and custom commands appear in the generated buildsystem and in IDEs. Lift such limitations by allowing INTERFACE libraries to have SOURCES. For those with sources, add a corresponding build target to the generated buildsystem. Fixes: #19145
generated by cgit v0.12 at 2025-08-29 12:31:03 (GMT)