summaryrefslogtreecommitdiffstats
path: root/Help/variable
Commit message (Collapse)AuthorAgeFilesLines
* cmake: Allow CMAKE_TOOLCHAIN_FILE to be set by environment variableBrad King2021-06-031-0/+3
| | | | | When no `CMAKE_TOOLCHAIN_FILE` is explicitly specified while creating a new build tree, check for an environment variable of the same name.
* Launchers: Support setting linker launchersBobby D Reynolds2021-05-281-0/+11
| | | | Fixes: #18316
* CMAKE_CFG_INTDIR: Formally deprecate in favor of $<CONFIG>Kyle Edwards2021-05-271-5/+6
|
* CPack: Implement new variable CPACK_CUSTOM_INSTALL_VARIABLESNils Gladitz2021-05-231-0/+42
| | | | | | The new variable allows projects to define custom key=value pairs of variables to be set in CPack cmake_install.cmake script invocations. This allows install(SCRIPT|CODE) to be parameterized at runtime.
* Help: Clarify calling cmake_minimum_required() inside a functionCraig Scott2021-05-151-1/+2
| | | Fixes: #21519
* Merge topic 'helpctestscript'Brad King2021-05-111-0/+5
|\ | | | | | | | | | | | | 140fe8c3c6 Help: Document CTEST_SCRIPT_DIRECTORY variable Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !6111
| * Help: Document CTEST_SCRIPT_DIRECTORY variableMichael Hirsch2021-05-101-0/+5
| |
* | Help: Fix typos and spelling in documentationJosef Angstenberger2021-05-073-3/+3
| |
* | Help: Document CMAKE_TLS_VERIFY variable explicitlyMichael Hirsch2021-05-041-0/+17
|/ | | | | Previously it was mentioned only in the `file` and `ExternalProject` documentation.
* CUDA: Add CMAKE_CUDA_HOST_COMPILER support on Windows non-VS generatorsunknown2021-04-221-0/+4
|
* Help: Fix typo in CMAKE_TOOLCHAIN_FILE docsAlbrecht Schlosser2021-04-171-1/+1
|
* Merge topic 'add_toolchain_cmake_option'Brad King2021-04-161-0/+3
|\ | | | | | | | | | | | | | | d5c3e4ac32 cmake: add support for --toolchain command argument 13838bbb36 CMAKE_TOOLCHAIN_FILE: Document relative path behavior Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5991
| * CMAKE_TOOLCHAIN_FILE: Document relative path behaviorRobert Maynard2021-04-151-0/+3
| |
* | Merge topic 'ios-rpath-linker-flag'Brad King2021-04-071-1/+1
|\ \ | |/ |/| | | | | | | | | 4aed96e230 Apple: Set CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG on non-macOS too Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5980
| * Apple: Set CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG on non-macOS tooCraig Scott2021-04-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since CMake 3.19, we no longer support macOS SDKs older than 10.5, which corresponds to Xcode 3. Supporting older Xcode versions for device platforms is also not realistic. We therefore expect the -rpath linker option should always be supported now. When targeting iOS, tvOS or watchOS, the previous disabling of -rpath support meant that the install_name_dir of shared libraries and frameworks was unable to use @rpath. This resulted in embedding absolute paths for their install_name. When they were embedded in an app bundle, this would cause the app to fail at runtime. By enabling the -rpath linker option, the default install_name_dir is now @rpath for these platforms, which results in binaries that do work at runtime. Fixes: #20036
* | Merge topic 'add_q_namespace_export_docs'Brad King2021-04-061-1/+1
|\ \ | | | | | | | | | | | | | | | | | | 3538f1c69b Help: Add Q_NAMESPACE_EXPORT to CMAKE_AUTOMOC_MACRO_NAMES default values Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5982
| * | Help: Add Q_NAMESPACE_EXPORT to CMAKE_AUTOMOC_MACRO_NAMES default valuesAlexander Neumann2021-04-051-1/+1
| |/ | | | | | | | | | | This was accidentally left out of commit 426941c433 (Autogen: Recognize the new Q_NAMESPACE_EXPORT macro in AUTOMOC, 2020-02-26, v3.17.0-rc2~3^2).
| * Merge topic 'doc-CMAKE_APPLE_SILICON_PROCESSOR' into release-3.20Brad King2021-04-011-3/+2
| |\ | | | | | | | | | | | | | | | | | | 3f04f69733 Help: CMAKE_APPLE_SILICON_PROCESSOR cannot be set in a toolchain file Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5965
* | \ Merge topic 'fujitsu-compiler-4.0-support'Brad King2021-04-011-0/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8ef55dec29 Help: Add release notes for Fujitsu compiler support 4c74c86f40 FindBLAS/LAPACK: Add support for the Fujitsu SSL2 library 376c300b25 FindOpenMP: Add support for Fujitsu compilers 9e0a1cf03e FindMPI: Add support for the Fujitsu compiler wrappers a237450948 Tests: Update for the FujitsuClang compiler 27579e9cf1 FujitsuClang: Add support for the Fujitsu compiler in Clang mode a55feff69c Tests: Update for the Fujitsu compiler 3c867cff4a Fujitsu: Add support for the Fujitsu compiler in Trad mode Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Axel Huebl <axel.huebl@plasma.ninja> Acked-by: Gilles Gouaillardet <gilles@rist.or.jp> Merge-request: !5954
| * | | FujitsuClang: Add support for the Fujitsu compiler in Clang modeChuck Atkins2021-03-311-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | This should be front end compatible with vanilla clang but giving it a unique identifier allows a project to pass additional options unique to Fujitsu and outside the scope of a CMake builtin.
| * | | Fujitsu: Add support for the Fujitsu compiler in Trad modeChuck Atkins2021-03-301-0/+1
| | | | | | | | | | | | | | | | Co-Author: Yuichiro Utsumi <utsumi.yuichiro@jp.fujitsu.com>
* | | | Merge topic 'doc-CMAKE_APPLE_SILICON_PROCESSOR'Brad King2021-04-011-3/+2
|\ \ \ \ | |/ / / |/| | / | | |/ | |/| | | | | | | 3f04f69733 Help: CMAKE_APPLE_SILICON_PROCESSOR cannot be set in a toolchain file Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5965
| * | Help: CMAKE_APPLE_SILICON_PROCESSOR cannot be set in a toolchain fileBrad King2021-04-011-3/+2
| | | | | | | | | | | | | | | | | | | | | `CMakeDetermineSystem` determines the host system information before loading the toolchain file. Issue: #22012
* | | project: Define variables indicating whether project is top levelfriendlyanon2021-03-262-0/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | Define `PROJECT_IS_TOP_LEVEL` and `<PROJECT-NAME>_IS_TOP_LEVEL`. The latter is a STATIC cache entry just like other `<PROJECT-NAME>_*` variables so that it is globally scoped. Issue: #20310 Fixes: #21961
* | | Merge topic 'vs-custom-flag-table'Brad King2021-03-231-0/+24
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 608ef8a6fc VS: Add a mostly-undocumented hook to load custom JSON flag tables 8dd8d63665 Tests: Add RunCMake hook to describe test variants Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5895
| * | | VS: Add a mostly-undocumented hook to load custom JSON flag tablesBrad King2021-03-221-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The names and formats of our VS flag tables are internal implementation details. However, some institutions need to maintain support for non-public VS platforms and toolsets. Provide a hook that their projects can use to load custom flag table files. This helps avoid distributing a custom CMake package within such institutions. Document the hook itself, but explicitly specify that the files the hook loads are not considered a stable interface.
* | | | Merge topic 'doc-xcoff-chrpath'Brad King2021-03-231-6/+13
|\ \ \ \ | |/ / / |/| | / | | |/ | |/| | | | | | | 4a9fb82030 Help: CMAKE_NO_BUILTIN_CHRPATH applies to XCOFF too Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5925
| * | Help: CMAKE_NO_BUILTIN_CHRPATH applies to XCOFF tooCraig Scott2021-03-221-6/+13
| | |
| * | Merge topic 'vs-toolset-version' into release-3.20Brad King2021-03-151-0/+20
| |\ \ | | |/ | | | | | | | | | | | | | | | | | | | | | 30c835428f VS: Accept and translate '-T version=' values with three components 58a50a3a0a VS: Fix '-T version=14.28' under VS 16.9 09f59da7f0 cmGlobalVisualStudioVersionedGenerator: Clarify local variable name Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5903
* | | VS: switch to new folder structure while keeping the old one workingMarcel Ritzschke2021-03-181-7/+6
| | | | | | | | | | | | Fixes: #21170
* | | Help: Document that CMAKE_<LANG>_FLAGS[_INIT] are stringsAlexander Richardson2021-03-172-0/+5
| | | | | | | | | | | | Issue: #21944
* | | Merge topic 'vs-toolset-version'Brad King2021-03-151-0/+20
|\ \ \ | |/ / |/| / | |/ | | | | | | | | | | 30c835428f VS: Accept and translate '-T version=' values with three components 58a50a3a0a VS: Fix '-T version=14.28' under VS 16.9 09f59da7f0 cmGlobalVisualStudioVersionedGenerator: Clarify local variable name Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5903
| * VS: Accept and translate '-T version=' values with three componentsBrad King2021-03-121-0/+12
| | | | | | | | | | | | | | | | The VS 16.8 and VS 16.9 toolset versions differ only in their third component. The `vcvarsall` option `-vcvars_ver=` accepts a three component version, so accept this format for VS toolset selection too. Issue: #21922
| * VS: Fix '-T version=14.28' under VS 16.9Brad King2021-03-121-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CMake accepts the toolset version that is default in the current VS version by matching the name later VS versions will use for the SxS props files. It predicts the future name based on the first two components of the current VS version's default toolset. However, this heuristic breaks naming the VS 16.8 toolset version 14.28 under VS 16.9 because the latter's default toolset version is 14.28.29910, which did not increment the second version component (unprecedented in VS). Fix this by always using the requested version's SxS props file when it exists, even if it matches the first two components of the current VS version's default toolset. Also add a special case for the name VS 16.10 will use for VS 16.9's default toolset, so that it can be used with VS 16.9 too. Fixes: #21922
* | Help: Document CMAKE_ANDROID_NDK_VERSION variableBrad King2021-03-031-0/+8
| |
* | Help: clarify availability of the MSVC_IDE variableBen Boeckel2021-02-111-0/+7
| |
* | Help: Update Sphinx versionadded directives for 3.20 releaseBrad King2021-02-101-0/+2
| | | | | | | | | | | | | | | | | | Run the script: Utilities/Sphinx/update_versions.py --since v3.19.0 --overwrite Manually restore the 3.20 version for `cmake_path`, which was originally part of 3.19 but reverted and restored in 3.20.
* | IntelLLVM: Add support for Intel LLVM-based compilersWilliam R. Dieter2021-01-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Using a single ID 'IntelLLVM' for the suite of Intel compilers based on the LLVM backend. The 'IntelLLVM' ID are used for C, C++, and Fortran. Data Parallel C++ will be handled in a separate commit. The C and C++ definitions are based on the Clang definitions. The Intel LLVM-based C and C++ compilers are based on the Clang front end, so existing Clang options are more likely to be a good match than options for the older Intel compilers. Fortran is based on the older Fortran front end with the LLVM backend. It has a similar interface to the older versions, though many options are shared with the C and C++ compilers. Fixes: #21561 Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
* | NVHPC: Add support for NVIDIA HPC SDK compilers based on PGITin Huynh2021-01-271-0/+1
| | | | | | | | | | | | | | Identify the compilers as `NVHPC` to distinguish it from the older PGI compilers from which they evolved, and from other `NVIDIA` compilers. Fixes: #20887
* | Help: Clarify meaning of CMAKE_SYSTEM_PROCESSORBrad King2021-01-261-4/+9
| | | | | | | | | | | | | | On Windows the value may not match the compiler's target architecture. Update the documentation to state this explicitly. Issue: #15170
* | Help: Document intended purpose of XCODE_ATTRIBUTE_<an-attribute>Brad King2021-01-221-2/+8
| | | | | | | | | | | | Also warn the reader against setting values CMake normally generates. Issue: #21728
* | Merge topic 'vs-sdk-selection'Brad King2021-01-211-1/+1
|\ \ | |/ | | | | | | | | | | 1e67482daf VS: Generalize Win10 max SDK version to all VS generators Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5721
| * VS: Generalize Win10 max SDK version to all VS generatorsjonathan molinatto2021-01-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | The `CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION_MAXIMUM` variable added in CMake 3.19 by commit ba497111f6 (VS: Add option for custom Win10 SDK version maximum, 2020-08-20, v3.19.0-rc1~262^2) was documented as if it worked for all generators but implemented only to override CMake's builtin default for the VS 2015 max SDK version. Generalize the variable to set a custom max SDK version for later VS versions too. Fixes: #21720
* | Help: Clarify memory check sanitizer option behavior for `log_path`Pawel Dac2021-01-131-0/+5
| | | | | | | | | | Added information about prepending [ASAN/LSAN/TSAN/MSAN/UBSAN]_OPTIONS to MemoryTesterEnvironmentVariable and `log_path` limitation.
* | Help: Add example for setting default CMAKE_CUDA_ARCHITECTURES valueRaul Tambre2021-01-101-0/+15
| | | | | | | | Fixes #21302 and #21666.
* | Merge topic 'reword_MSVC_documentation'Brad King2021-01-081-3/+2
|\ \ | | | | | | | | | | | | | | | | | | 1185438ea8 Help: Reword the MSVC variable documentation focusing on cl.exe compatibility Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5676
| * | Help: Reword the MSVC variable documentation focusing on cl.exe compatibilityThomas Bernard2021-01-071-3/+2
| | | | | | | | | | | | Fixes: #21651
* | | CMAKE_EXPORT_COMPILE_COMMANDS: allow configuration per targetShannon Booth2021-01-051-1/+2
|/ / | | | | | | | | | | | | | | The new target property `EXPORT_COMPILE_COMMANDS` associated with the existing global variable can be used to optionally configure targets for their compile commands to be exported. Fixes: #19462
* | Merge topic 'unity-anon-ns'Craig Scott2020-12-161-0/+6
|\ \ | | | | | | | | | | | | | | | | | | 0fe9c40494 Unity Build: Add option for generating per-file unique id Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4784
| * | Unity Build: Add option for generating per-file unique idStephen Kelly2020-12-151-0/+6
| | | | | | | | | | | | Fixes: #21477