summaryrefslogtreecommitdiffstats
path: root/Help/variable
Commit message (Collapse)AuthorAgeFilesLines
* Help: Document CMAKE_MATCH_<n> variablesBrad King2017-04-182-3/+14
|
* Merge topic 'ipo-var-per-config'Brad King2017-04-181-0/+8
|\ | | | | | | | | | | | | 470437f6 Support CMAKE_INTERPROCEDURAL_OPTIMIZATION_<CONFIG> Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !709
| * Support CMAKE_INTERPROCEDURAL_OPTIMIZATION_<CONFIG>Ruslan Baratov2017-04-171-0/+8
| |
* | Merge topic 'vs-custom-kits-dir'Brad King2017-04-171-0/+5
|\ \ | |/ |/| | | | | | | | | | | fee01194 VS: Add an environment variable for the Windows 10 kits directory b80c6d12 VS: Refactor Win 10 Kits root detection to support multiple roots Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !696
| * VS: Add an environment variable for the Windows 10 kits directoryBrad King2017-04-121-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Define a `CMAKE_WINDOWS_KITS_10_DIR` environment variable to allow users to tell CMake about a custom Windows 10 SDK directory. We choose to make this an environment variable rather than a CMake variable or cache entry because: * Using a custom directory also requires custom external MSBuild configuration. Therefore users are already configuring a custom environment. * The custom directory must be set consistently in all parts of a build including nested projects. An environment variable avoids requiring users to thread the setting into nested builds. Fixes: #16743
* | Merge topic 'project-description'Brad King2017-04-132-0/+13
|\ \ | |/ |/| | | | | | | | | 3b484871 project: Add `DESCRIPTION` parameter Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !679
| * project: Add `DESCRIPTION` parameterAlex Turbov2017-04-112-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is quite often the project description has used in a real world software. Examples include: * part of a help screen of the application * builtin resources (`*.rc` files, data for "About" dialog of a GUI app, & etc) * most generators for CPack can use it * it could be used by documentary software (Doxygen, Sphinx) which is usually integrated to CMake based projects via `add_custom_target()` Now `project()` call learned an optional `DESCRIPTION` parameter with a short string describing a project. Being specified, it would set the `PROJECT_DESCRIPTION` variable which could be used in `configure_file()` or whatever user wants. Also `PROJECT_DESCRIPTION` is a default value for `CPACK_PACKAGE_DESCRIPTION_SUMMARY`.
* | Rename CMAKE_GCC_{AR,RANLIB} to CMAKE_LANG_COMPILER_{AR,RANLIB}Ruslan Baratov2017-04-032-6/+6
|/ | | | | | The variables recently added by commit b9d36826 (Add 'CMAKE_GCC_AR' and 'CMAKE_GCC_RANLIB' variables, 2017-03-08) are more appropriately managed with language-specific names rather than toolchain-specific names.
* Merge topic 'doc-prefer-MSVC_VERSION'Brad King2017-03-2310-2/+22
|\ | | | | | | | | | | | | | | | | fecf8467 Help: Document preference of `MSVC_VERSION` over `MSVC##` 712452e3 Help: Clarify MSVC14 docs w.r.t. VS 2017 v141 toolset 49a60b70 MSVC: Exclude future cl 20+ from MSVC14 variable Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !609
| * Help: Document preference of `MSVC_VERSION` over `MSVC##`Brad King2017-03-2210-0/+20
| | | | | | | | Issue: #16735
| * Help: Clarify MSVC14 docs w.r.t. VS 2017 v141 toolsetBrad King2017-03-221-2/+2
| | | | | | | | Issue: #16735
* | Help: Document VS generator toolset specification syntaxBrad King2017-03-131-1/+23
| |
* | Help: Cross-reference generator toolset variablesBrad King2017-03-132-0/+8
| |
* | Help: Cross-reference generator platform variablesBrad King2017-03-132-0/+7
| |
* | Help: Move generator toolset support details to variable docsBrad King2017-03-131-5/+12
| | | | | | | | | | | | | | Move the details about support for generator toolset specification to the `CMAKE_GENERATOR_TOOLSET` variable documentation. This is a more suitable place because it is shared by all means to set this variable, not just the `cmake -T` option.
* | Help: Move generator platform support details to variable docsBrad King2017-03-131-1/+8
| | | | | | | | | | | | | | Move the details about support for generator platform specification to the `CMAKE_GENERATOR_PLATFORM` variable documentation. This is a more suitable place because it is shared by all means to set this variable, not just the `cmake -A` option.
* | Merge topic 'doc-toolset-host-arch-typo'Brad King2017-03-131-1/+1
|\ \ | | | | | | | | | | | | | | | | | | 81b24547 Help: Fix typo in CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTURE Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !579
| * | Help: Fix typo in CMAKE_VS_PLATFORM_TOOLSET_HOST_ARCHITECTUREBrad King2017-03-131-1/+1
| | |
* | | Merge topic 'xcode-test-schema-generation'Brad King2017-03-131-0/+11
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3fd9f4ab Xcode: Add test for schema generation cf13e495 Xcode: Control schema generation via variable Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !577
| * | | Xcode: Control schema generation via variableGregor Jasny2017-03-121-0/+11
| | | | | | | | | | | | | | | | Issue: #15441
* | | | Merge topic 'cuda-vs'Brad King2017-03-131-0/+12
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 65481a60 CUDA: Work around VS limitation in CudaOnly.WithDefs test 8cae24a1 VS: Add more CUDA flag table entries 6ca4f222 VS: Add support for the CUDA_SEPARABLE_COMPILATION property 94255511 VS: Select CUDA code generation architectures 253594d0 VS: Select the CUDA runtime library 4def02a3 VS: Place CUDA host compiler options in proper project file fields 29f07b08 VS: Do not pass CUDA compile options to C compiler b966f489 VS: Do not use absolute paths to CUDA sources ... Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !566
| * | | VS: Select highest available CUDA toolset by defaultBrad King2017-03-101-2/+4
| | | | | | | | | | | | | | | | | | | | If `CMAKE_GENERATOR_TOOLSET` does not have a `cuda=...` field then find available CUDA toolsets and choose the highest version.
| * | | VS: Provide an option to specify CUDA toolset versionBrad King2017-03-101-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The NVIDIA CUDA Toolkit provides MSBuild toolset files for integration with Visual Studio. Multiple versions may be installed so we need a way to tell our VS generators which CUDA toolset to use. Extend the `CMAKE_GENERATOR_TOOLSET` specification to provide a `cuda=...` field specifying the version number.
* | | | Merge topic 'pr.gcc_ar'Brad King2017-03-102-0/+14
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b9d36826 Add 'CMAKE_GCC_AR' and 'CMAKE_GCC_RANLIB' variables Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !550
| * | | | Add 'CMAKE_GCC_AR' and 'CMAKE_GCC_RANLIB' variablesRuslan Baratov2017-03-082-0/+14
| |/ / /
* | | | Merge topic 'master'Brad King2017-03-091-0/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d9bdcf34 Tests: Add x32 tests to test suite 5b6d354f Help: Add notes for topic 'x32-abi' bed9c73d Modules: Add x32-abi support to hard-coded paths 462cf254 Add support for x32-abi Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !532
| * | | | Add support for x32-abiSteven Newbury2017-03-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Detect x32-abi through CMakeCompilerABI infrastruture and use this information at runtime to determine the correct library paths with `FIND_LIBRARY_USE_LIBX32_PATHS`. Fixes: #15994
* | | | | Merge topic 'doc-vs15-MSVC_VERSION'Brad King2017-03-091-1/+2
|\ \ \ \ \ | |_|/ / / |/| | | / | | |_|/ | |/| | | | | | | | | | 66542b66 Help: Update MSVC_VERSION for Visual Studio 2017 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !567
| * | | Help: Update MSVC_VERSION for Visual Studio 2017Wojciech Mamrak2017-03-081-1/+2
| | |/ | |/| | | | | | | | | | | | | The value we documented was left from a preview that still used `v140` tools. Update it to match the `v141` tools distributed with the final release.
* | | Add variable 'CMAKE_INTERPROCEDURAL_OPTIMIZATION'Ruslan Baratov2017-03-021-0/+8
| |/ |/|
* | Merge topic 'autogen_uic_paths'Brad King2017-03-021-0/+11
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3bf28f5e Autogen: New short InfoGet functions 154d8339 Autogen: Parse enabled feature configuration only ac77fa35 Autogen: Add missing return on error 662ad240 Autogen: Rename and merge moc related methods 5adf22bb Autogen: Add AUTOUIC_SEARCH_PATHS release notes 36fa535d Autogen: Add AUTOUIC_SEARCH_PATHS documentation 6d7c02db Autogen: Add AUTOUIC_SEARCH_PATHS test 1cdf7c1b Autogen: Add AUTOUIC_SEARCH_PATHS support 110c1bf4 Autogen: Add subDirPrefix function db431ecf Autogen: Merge FindInIncludeDirectories into FindIncludeFile
| * | Autogen: Add AUTOUIC_SEARCH_PATHS documentationSebastian Holtermann2017-03-021-0/+11
| | |
* | | find_library: Allow custom lib suffix be used as find pathChristian Schmidbauer2017-03-011-0/+11
|/ / | | | | | | | | | | | | | | | | | | Add a new `CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX` variable to allow use of a custom suffix on `lib` directory names. This is a more general option than that added by commit v3.7.0-rc1~504^2 (Teach find_library and find_package to search lib32 paths, 2016-06-10). It allows the find path to be more deterministic on custom setups. See discussion in #10287 and #15994.
* | Autogen: Add AUTOMOC_DEPEND_FILTERS documentationSebastian Holtermann2017-02-231-0/+12
| |
* | Merge topic 'install_name_policy'Brad King2017-02-171-0/+7
|\ \ | |/ |/| | | | | | | | | | | 1ba91291 Add policy CMP0068 separate install_name and RPATH settings on macOS f7b9bf41 Apple: Add BUILD_WITH_INSTALL_NAME_DIR target property 4bff2d14 Apple: Refactor support for using INSTALL_NAME_DIR. 624fb9d7 Help: Format BUILD_WITH_INSTALL_RPATH documentation
| * Apple: Add BUILD_WITH_INSTALL_NAME_DIR target propertyClinton Stimpson2017-02-141-0/+7
| | | | | | | | | | This new property controls whether to apply INSTALL_NAME_DIR to the build tree. It also overrides BUILD_WITH_INSTALL_RPATH.
* | CUDA: Detect the toolkit include directoriesRobert Maynard2017-02-101-0/+7
|/ | | | | The `nvcc -v` output provides what include directories need to be added to use the CUDA toolkit from other languages ( C/C++ ).
* Merge topic 'lang_lint'Brad King2017-01-251-0/+6
|\ | | | | | | | | 0618ddf6 Add properties to run the cpplint style checker with the compiler
| * Add properties to run the cpplint style checker with the compilerJamie Snape2017-01-231-0/+6
| | | | | | | | | | | | Create a `<LANG>_CPPLINT` target property (initialized by a `CMAKE_<LANG>_CPPLINT` variable) to specify a `cpplint` style checker command line to be run along with the compiler.
* | Help: Fix typo in CMAKE_DL_LIBS docsThiago Perrotta2017-01-241-1/+1
|/
* ctest_memcheck: add support for standalone LeakSanitizerJamie Snape2017-01-091-1/+1
|
* Help: Clarify meaning of CMAKE_CL_64Brad King2016-12-141-2/+3
| | | | Closes: #16504
* Help: Document CUDA_STANDARD and related propertiesRobert Maynard2016-12-094-0/+34
|
* try_compile: Add policy CMP0067 to honor language standardsBrad King2016-12-061-0/+2
| | | | | | | | | | | | | | Projects use `try_compile` to check if they will be able to compile some particular source code. When a language standard variable like `CMAKE_CXX_STANDARD` is set, then the project intends to compile source code using a compiler mode for that standard. Therefore it makes sense for `try_compile` to use that standard in the test project too. Unfortunately this was not done when support for the `CMAKE_CXX_STANDARD` variable was first implemented. Add a policy to introduce the improved behavior in a compatible way. Closes: #16456
* Merge topic 'vs-default-build-package'Brad King2016-11-291-0/+8
|\ | | | | | | | | 9e3164df VS: Add option to place `PACKAGE` target in solution default build
| * VS: Add option to place `PACKAGE` target in solution default buildMichael Stürmer2016-11-291-0/+8
| | | | | | | | | | Add a `CMAKE_VS_INCLUDE_PACKAGE_TO_DEFAULT_BUILD` variable to control this behavior.
* | Merge topic 'doc-CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT'Brad King2016-11-222-0/+16
|\ \ | |/ |/| | | | | df9fea7f Help: Document CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT variable
| * Help: Document CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT variableBrad King2016-11-212-0/+16
| | | | | | | | | | | | This variable documentation was simply missing. Suggested-by: Craig Scott <craig.scott@crascit.com>
* | Android: Add CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINEBrad King2016-11-143-2/+13
| | | | | | | | | | | | | | | | Expose the binutils' machine name (typically used as a prefix on the tool names) publicly. This is expected to match the `gcc -dumpmachine` value. Suggested-by: Ruslan Baratov <ruslan_baratov@yahoo.com>
* | Android: Add CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG variableBrad King2016-11-141-0/+6
| | | | | | | | | | | | | | | | | | The NDK provides prebuilt toolchain files in directories named for the host architecture. The NDK build system calls this `HOST_TAG`. Expose the value publicly for use by clients that need to pass it to external tools. Suggested-by: Ruslan Baratov <ruslan_baratov@yahoo.com>
generated by cgit v0.12 at 2024-10-20 23:51:57 (GMT)