summaryrefslogtreecommitdiffstats
path: root/Help/variable
Commit message (Collapse)AuthorAgeFilesLines
* CodeBlocks: add option to exclude external filesAlexandr (Sagrer) Gridnev2017-09-141-0/+7
| | | | | | | | | | | | Add variable `CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES` to optionally exclude files from outside the project root from the project file written by the CodeBlocks extra generator. This optionally restores logic that had been removed by commit v2.8.3~40^2 (CodeBlocks Generator: Do not omit files in the project file listing, 2010-10-05) in response to QTCREATORBUG-2250. Issue: #12110 Fixes: #17188
* Flang: Add support for flang Fortran compilerTin Huynh2017-08-311-0/+1
| | | | | | | | | | | | | | flang is a Fortran compiler built on top of clang [1]. Because flang shares a lot of commonalities with clang, the flang module piggybacks off the clang module and overrides certain options. Add flang to Fortran compiler auto find list. Update flang preprocessor macros to differentiate from PGI. Add Flang-FindBinUtils. [1] https://github.com/flang-compiler/flang
* Help: Cross-reference and clarify CMAKE_FIND_NO_INSTALL_PREFIX docsBrad King2017-08-302-12/+19
| | | | Suggested-by: Luke Yeager <lukeyeager@users.noreply.github.com>
* Add properties to run cppcheck along with the compilerBill Hoffman2017-08-301-0/+6
| | | | | | Create a `<LANG>_CPPCHECK` target property (initialized by a `CMAKE_<LANG>_CPPCHECK` variable) to specify a `cppcheck` command line to be run along with the compiler.
* Autogen: Add documentation for AUTOMOC_MACRO_NAMESSebastian Holtermann2017-08-181-0/+19
|
* Merge topic 'labels-for-subprojects'Brad King2017-07-132-0/+11
|\ | | | | | | | | | | | | | | | | | | | | 376dc3eb Help: Add notes for topic 'labels_for_subprojects' a70d8e93 Add tests for new directory labels and labels-for-subprojects features 47b3a57c Display subproject timing summary d3859624 Add directory property 'LABELS' and CMAKE_DIRECTORY_LABELS variable d08ec4d2 Add CTEST_LABELS_FOR_SUBPROJECTS as a CTest module and script variable Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1004
| * Add directory property 'LABELS' and CMAKE_DIRECTORY_LABELS variableBetsy McPhail2017-07-101-0/+6
| | | | | | | | | | The specified LABELS will be passed down to subdirectories as well as any targets or tests in the directory.
| * Add CTEST_LABELS_FOR_SUBPROJECTS as a CTest module and script variableBetsy McPhail2017-07-101-0/+5
| | | | | | | | | | Use this variable to specify a list of labels that will be reported to CDash as subprojects.
* | Merge topic 'iar_improved'Brad King2017-07-072-0/+9
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | d8e6cd9e IAR: Improve support for IAR ARM Compiler 0b1a2876 Add a CMAKE_<LANG>_COMPILER_ARCHITECTURE_ID variable fea7d69d Store CMAKE_ASM_COMPILER_VERSION persistently d2a8b5ce CMakeDetermineASMCompiler: Fix small copy-paste mistake a2112257 Add infrastructure to use language extensions without any standard 8cd28bb0 cmLocalGenerator: Switch order of <LANG>_{EXTENSIONS,STANDARD} check 0fc2d78e cmLocalGenerator: Simplify logic for language standard or extension flag Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !991
| * IAR: Improve support for IAR ARM CompilerNorbert Lange2017-06-291-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make the implementation for this compiler more complete. IAR has multiple C++ modes, historically they were reduced c++ versions for embedded that gradually improved to the full standard (which can be reduced again by e.g. disabling rtti and exceptions). The new implementation picks the best available, but the c++ mode can also be overridden by defining `CMAKE_IAR_CXX_FLAG`. Add C/C++ standard flags so that all modes up to and including the last supported standard are defined. Fixes: #16826
| * Add a CMAKE_<LANG>_COMPILER_ARCHITECTURE_ID variableNorbert Lange2017-06-291-0/+8
| | | | | | | | | | | | | | | | | | | | Compilers such as MSVC and IAR may have variants that target different architectures. We have been using a `MSVC_<LANG>_ARCHITECTURE_ID` variable to hold this information for MSVC. Add an alternative with a more general name (later we can port MSVC to it too). This additional information may be needed to generate proper invocations of the compiler based on its architecture variant.
* | Help: Document the CMAKE_MSVCIDE_RUN_PATH variable.Robert Maynard2017-06-271-0/+10
|/
* Merge topic 'android-unified-headers'Brad King2017-06-131-0/+9
|\ | | | | | | | | | | | | 3d00be13 Android: Add support for unified headers Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !956
| * Android: Add support for unified headersBrad King2017-06-121-0/+9
| | | | | | | | | | | | | | | | The unified headers are preferred as of NDK r15, so use them by default if available and provide an option to use the deprecated headers. Inspired-by: Florent Castelli <florent.castelli@gmail.com> Fixes: #16584
* | CUDA: Add option to run the compiler through launcher toolsBrad King2017-06-091-1/+1
|/ | | | | | | | Add a `CUDA_COMPILER_LAUNCHER` target property like those added for C and CXX by commit v3.4.0-rc1~450^2 (Add options to launch the compiler through tools like ccache or distcc, 2015-06-04). Fixes: #16953
* Help: Add a hint about C and C++ compiler version variableGregor Jasny2017-05-281-0/+4
| | | | Closes #16917
* Add options for separate compile and link sysrootsBrad King2017-05-093-0/+21
| | | | | | | | | Add `CMAKE_SYSROOT_COMPILE` and `CMAKE_SYSROOT_LINK` variables to as operation-specific alternatives to `CMAKE_SYSROOT`. This will be useful for Android NDKs that compile and link with different sysroot values (e.g. `r14` with unified headers). Co-Author: Florent Castelli <florent.castelli@gmail.com>
* Help: Fix CMAKE_HOST_WIN32 documentationChristian Pfeiffer2017-04-241-2/+2
| | | | | | The documentation falsely claims `CMAKE_HOST_WIN32` is `true` on Cygwin. Since commit v2.8.4~153^2 (Cygwin: Do not define 'WIN32', 2010-12-17) we do not define `CMAKE_HOST_WIN32` on Cygwin either.
* Drop Visual Studio 7 .NET 2003 generatorBrad King2017-04-194-4/+4
| | | | This generator has been deprecated since CMake 3.6. Remove it.
* 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
generated by cgit v0.12 at 2025-01-08 21:00:33 (GMT)