summaryrefslogtreecommitdiffstats
path: root/Help/variable
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'doc-find-path-variables'Brad King2015-06-2514-97/+88
|\ | | | | | | | | 3117b5fe Help: Revise CMAKE_*_PATH and CMAKE_SYSTEM_*_PATH variable docs (#15631)
| * Help: Revise CMAKE_*_PATH and CMAKE_SYSTEM_*_PATH variable docs (#15631)Brad King2015-06-2514-97/+88
| | | | | | | | | | Improve reStructuredText formatting and cross-references. Specify explicitly that each variable may be set to a ;-list of multiple values.
* | Merge topic 'ConcurrentFortran-compiler-id'Brad King2015-06-191-0/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 54676a0e Help: Add notes for topic 'ConcurrentFortran-compiler-id' 7cd539b1 Add support for Concurrent Fortran 77 Compiler 0d204c1c CMakeDetermineCompilerId: Try matching compiler output to detect id 5f0dad75 CMakeDetermineCompilerId: Refactor id build/check loop logic c65a060e CMakeDetermineCompilerId: Optionally try some flags before no flags
| * | Add support for Concurrent Fortran 77 CompilerBrad King2015-06-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | The Concurrent Fortran compiler (ccur.com) is available on Linux and can be used much like the GNU Fortran compiler. Currently it has no preprocessor symbols to identify it so we need to detect it by matching compiler output. Suggested-by: Anthony Ette <Anthony.R.Ette@controlsdata.com>
* | | Merge topic 'doc-CMAKE_GENERATOR_PLATFORM-typo'Brad King2015-06-191-1/+1
|\ \ \ | |/ / |/| | | | | | | | 1c9db7db Help: Fix typo in CMAKE_GENERATOR_PLATFORM docs (#15621)
| * | Help: Fix typo in CMAKE_GENERATOR_PLATFORM docs (#15621)Brad King2015-06-181-1/+1
| |/ | | | | | | s/toolset/platform/
* | Merge topic 'compiler-launcher'Brad King2015-06-151-0/+6
|\ \ | | | | | | | | | | | | 698f7597 Add options to launch the compiler through tools like ccache or distcc
| * | Add options to launch the compiler through tools like ccache or distccBill Hoffman2015-06-151-0/+6
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Create a <LANG>_COMPILER_LAUNCHER target property (initialized by a CMAKE_<LANG>_COMPILER_LAUNCHER variable) to specify a compiler launcher tool. This will supersede the CMAKE_<LANG>_COMPILER_ARG1 approach to using such tools. The old approach set CMAKE_<LANG>_COMPILER to the launcher tool while the new approach leaves this variable set to the actual compiler. Implement this property for Makefile and Ninja generators. It cannot be implemented for VS or Xcode generators as the IDE build tools offer no such hooks.
* | Help: Document CMAKE_FIND_APPBUNDLE and CMAKE_FIND_FRAMEWORKBrad King2015-06-082-0/+44
| | | | | | | | | | Add dedicated documents for these and link to them instead of duplicating their documentation in every find command.
* | Help: Document CMAKE_SYSTEM_APPBUNDLE_PATH variableBrad King2015-06-081-0/+7
| |
* | Help: Document CMAKE_SYSTEM_FRAMEWORK_PATH variableBrad King2015-06-081-0/+8
| |
* | Remove CMAKE_USE_RELATIVE_PATHS variable.Stephen Kelly2015-06-031-7/+2
|/ | | | | | | | | | | | | | | | | The test for this variable was removed in commit v2.8.8~330^2~7 (complex: Remove ancient unused ComplexRelativePaths test, 2011-12-23). Commit v3.1.0-rc1~425^2~2 (backtrace: Convert to local paths in IssueMessage, 2014-03-12) appears to have accidentally made some backtraces print relative paths with the variable because conversions which used to be done at configure time, before the variable had an effect are now potentially done at generate time. The documentation of the variable says not to use it, and the docs are wrong in that the variable actually applies in per-directory scope. The read of the variable makes it harder to split conversion methods from cmLocalGenerator where they don't belong. Remove it now.
* Help: Format visibility property and variable documentationBrad King2015-05-222-10/+4
| | | | Add reStructuredText markup appropriately.
* Add options to run include-what-you-use with the compilerBrad King2015-05-191-0/+6
| | | | | | Create a <LANG>_INCLUDE_WHAT_YOU_USE target property (initialized by a CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE variable) to specify an IWYU command line to be run along with the compiler.
* VS: Add option to put INSTALL target in .sln default buildRobert Goulet2015-05-061-0/+8
| | | | | Add a CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD variable to control this behavior.
* Help: Revise buildsystem artifact file type documentation (#15539)Brad King2015-04-296-6/+36
| | | | | | Add sections to the cmake-buildsystem(7) manual and cross-reference them with relevant variables and target properties. This avoids duplicating the information and allows it to be more detailed.
* Help: Clarify that CMAKE_SIZEOF_VOID_P is specific to the target machineNils Gladitz2015-04-231-1/+1
|
* Merge topic 'add-GreenHills-MULTI-generator'Brad King2015-04-207-0/+36
|\ | | | | | | | | | | | | 66b641f4 Help: Add notes for topic 'add-GreenHills-MULTI-generator' 48004d9d Add a 'Green Hills MULTI' generator on Windows 051d8be1 cmLocalGenerator: Constify some cmTarget and cmGeneratorTarget arguments
| * Add a 'Green Hills MULTI' generator on WindowsGeoff Viola2015-04-207-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | Green Hills MULTI is an IDE for embedded real-time systems. The IDE's product page can be found here: http://www.ghs.com/products/MULTI_IDE.html It supports cross compiling on ARM, Intel x86, and other architectures with various operating systems. The IDE exists on Linux and Windows host systems, but CMake will currently only generate the project files on Windows host systems.
* | Merge topic 'link-implicit-libs-full-path'Brad King2015-04-091-0/+2
|\ \ | |/ |/| | | | | | | | | 882f48e5 Link libraries by full path even in implicit directories 318cd370 Help: Add link target for Find Modules section of cmake-developer.7 1535dcd8 Tests: Teach RunCMake to optionally merge command output to stdout
| * Link libraries by full path even in implicit directoriesBrad King2015-04-091-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When CMP0003 was first introduced we wanted to link all libraries by full path. However, some projects had problems on platforms where find_library would find /usr/lib/libfoo.so when the project really wanted to link to /usr/lib/<arch>/libfoo.so and had been working by accident because pre-CMP0003 behavior used -lfoo to link. We first tried to address that in commit v2.6.0~440 (Teach find_library to avoid returning library paths in system directories, 2008-01-23) by returning just "foo" for libraries in implicit link directories. This caused problems for projects expecting find_library to always return a full path. We ended up using the solution in commit v2.6.0~366 (... switch library paths found in implicit link directories to use -l, 2008-01-31). However, the special case for libraries in implicit link directories has also proven problematic and confusing. Introduce policy CMP0060 to switch to linking all libraries by full path even if they are in implicit link directories. Explain in the policy documentation the factors that led to the original approach and now to this approach.
* | Merge topic 'emulator-property'Brad King2015-04-081-0/+12
|\ \ | | | | | | | | | | | | | | | | | | | | | 1975d53a Help: Add notes for topic 'emulator-property' 9160d6c2 TestGenerator: Add CROSSCOMPILING_EMULATOR support. e942526b try_run: Use CMAKE_CROSSCOMPILING_EMULATOR. 579c4bec Properties: Add CROSSCOMPILING_EMULATOR target property.
| * | try_run: Use CMAKE_CROSSCOMPILING_EMULATOR.Matt McCormick2015-04-081-2/+9
| | | | | | | | | | | | | | | | | | | | | If the CMAKE_CROSSCOMPILING_EMULATOR variable is defined, and CMAKE_CROSSCOMPILING is TRUE, then use CMAKE_CROSSCOMPILING_EMULATOR to run the try_run executables. This prevents the need to populate TryRunResults.cmake when cross compiling.
| * | Properties: Add CROSSCOMPILING_EMULATOR target property.Matt McCormick2015-04-071-0/+5
| |/ | | | | | | | | | | | | Add CROSSCOMPILING_EMULATOR target property for executables. This is used by subsequent patches to run exectuables created for the target system when crosscompiling. The property is initialized by the CMAKE_CROSSCOMPILING_EMULATOR variable when defined.
* | Help: Document supported compilers in cmake-compile-features.7Robert Maynard2015-04-078-8/+8
|/ | | | | | | Extend sentences in other documentation linking to this manual to say that it has a list of supported compilers. Co-Author: Brad King <brad.king@kitware.com>
* VS: Use $(ConfigurationName) as CMAKE_CFG_INTDIR in VS 7, 8, 9Brad King2015-02-161-5/+5
| | | | | | | | | This will allow us to use a value other than just the config name for the project OutputDirectory setting used for $(OutDir). Also use $(ConfigurationName) instead of $(OutDir) for the link directory configuration suffix since that is a hard-coded instance of a use case for CMAKE_CFG_INTDIR.
* Xcode: Switch to internal CMAKE_MAKE_PROGRAM lookup by generator (#15324)Brad King2015-01-291-2/+9
| | | | | | | | | | | | The "cmakexbuild" wrapper is not needed for Xcode 4 and above, and the path to it may change when CMake moves. Avoid storing a specific path to a build program in CMakeCache.txt and instead compute the value for CMAKE_MAKE_PROGRAM on demand. However, if a user does set the value explicitly then honor it. This does for Xcode what commit v3.0.0-rc1~260^2~4 (VS: Switch to internal CMAKE_MAKE_PROGRAM lookup by generators, 2013-11-15) did for Visual Studio generators.
* Help: add missing MINGW variable documentationBen Boeckel2015-01-211-0/+6
|
* Merge topic 'doc-CMAKE_FIND_PACKAGE_NAME'Brad King2015-01-121-0/+6
|\ | | | | | | | | | | 8435088d Help: Document CMAKE_FIND_PACKAGE_NAME variable b8abd258 find_package: Document CMAKE_FIND_PACKAGE_NAME variable
| * Help: Document CMAKE_FIND_PACKAGE_NAME variableBrad King2015-01-111-0/+6
| |
| * Merge branch 'doc-CMAKE_INSTALL_PREFIX-link-GNUInstallDirs' into releaseBrad King2014-11-121-0/+5
| |\
* | | Add 'ANDROID_API_MIN' target property to set Android Target MIN APIDmitry Polyanitsa2014-12-171-0/+5
| | | | | | | | | | | | | | | | | | Also add a 'CMAKE_ANDROID_API_MIN' variable to set the property default. Teach the VS generator to write the MIN API value into Nsight Tegra project files.
* | | Merge topic 'try_compile-link-flags'Brad King2014-12-081-0/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | 88eb5824 try_compile: Pass linker flags into test project (#14066) a4f9b6f0 CMakeDetermineCompilerABI: Use normal linker flags in ABI project
| * | | try_compile: Pass linker flags into test project (#14066)Brad King2014-12-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Copy CMAKE_EXE_LINKER_FLAGS into the test project generated by try_compile, just like we already copy CMAKE_<LANG>_FLAGS. Add CMake Policy CMP0056 to activate this behavior in a compatible way, but do not warn by default when the policy is not set since it will affect all try_compile calls. Extend the RunCMake.try_compile test with a case covering this behavior for each policy setting.
* | | | cmMakefile: store the number of last matches in a CMake varBen Boeckel2014-12-031-0/+8
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | With PushScope and PopScope, keeping track of another bit of data for each scope isn't easy. Instead, store it as another CMake variable so it gets implicitly tracked along with everything else. This works in a revert of commit 7d674b5f0b28a610333644d417c2e8cb796cc9e4.
* | | Merge topic 'doc-CMAKE_INSTALL_PREFIX-link-GNUInstallDirs'Brad King2014-11-121-0/+5
|\ \ \ | |/ / |/| / | |/ | | 00d4cdc9 Help: Link to GNUInstallDirs from CMAKE_INSTALL_PREFIX (#15246)
| * Help: Link to GNUInstallDirs from CMAKE_INSTALL_PREFIX (#15246)Brad King2014-11-121-0/+5
| | | | | | | | | | Add a note to the CMAKE_INSTALL_PREFIX documentation that refers readers to the GNUInstallDirs module to make the latter easier to discover.
* | Help: Document CMAKE_XCODE_ATTRIBUTE_<an-attribute> variable (#15215)Brad King2014-10-221-0/+10
|/
* ctest_memcheck: Add support for MemorySanitizer msanBill Hoffman2014-10-071-1/+1
|
* ctest_memcheck: Add support for UndefinedBehaviorSanitizer ubsanBen Boeckel2014-10-071-1/+1
| | | | | UBSan instruments a build and logs messages on any undefined behavior instances.
* ctest: add support for additional sanitizer optionsBen Boeckel2014-10-031-0/+5
| | | | | Sanitizers receive options through their environment variable; support user-specified options here.
* ctest: update documentation for CTEST_MEMORYCHECK_TYPEBen Boeckel2014-10-031-2/+3
| | | | | | The AddressSanitizer value was not documented. Also fix some typos.
* Add 'ANDROID_API' target property to set Android Target APIBrad King2014-09-301-0/+5
| | | | Also add a 'CMAKE_ANDROID_API' variable to set the property default.
* Add 'ANDROID_GUI' target property to mark Android applicationsBrad King2014-09-291-0/+5
| | | | | | | Also add a 'CMAKE_ANDROID_GUI' variable to set the property default so a project can easily make all executables Android applications. An Android application executable file has the same extension as a shared library (.so).
* VS: Teach VS >= 10 to recognize CMAKE_SYSTEM_NAME 'Android'Brad King2014-09-291-0/+7
| | | | | | | When CMAKE_SYSTEM_NAME is 'Android', check for an installation of 'NVIDIA Nsight Tegra Visual Studio Edition' and generate .vcxproj files for the "Tegra-Android" platform. Also make the installed version available in a CMAKE_VS_NsightTegra_VERSION variable.
* Merge topic 'vs-generator-platform'Brad King2014-09-151-0/+2
|\ | | | | | | | | | | | | | | | | be6a555d Tests: Test setting a generator platform in a toolchain file d506fee8 Tests: Use -A option to pass generator platform selection 11c9ddd6 ExternalProject: Use -A option to pass generator platform 29bd843e CTest: Use -A option to pass generator platform selection eb7d8156 cmake: Add -A option to specify a generator platform
| * cmake: Add -A option to specify a generator platformBrad King2014-09-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | Define the 'cmake -A' option to set CMAKE_GENERATOR_PLATFORM without having to spell out the whole variable name. We choose the name '-A' for "platform" because '-P' is already taken, and in the common use case the "platform" is actually an architecture (e.g. x64). Teach the RunCMake test infrastructure to use -A to pass the generator platform. Extend the RunCMake.GeneratorPlatform test with a case to verify that the -A option cannot be repeated.
* | Help: Document the WINCE variablePascal Bach2014-09-111-0/+5
|/
* CMake: Add CMAKE_GENERATOR_PLATFORM optionBrad King2014-09-051-0/+13
| | | | | | | | | | | Reject the option by default. It will be implemented on a per-generator basis. Pass the setting into try_compile project generation. Add cache entry CMAKE_GENERATOR_PLATFORM and associated variable documentation to hold the value persistently. Add a RunCMake.GeneratorPlatform test to cover basic use cases for the option. Verify that CMAKE_GENERATOR_PLATFORM is empty by default, and that it is rejected when the generator does not support a user setting.
* Help: Document CMAKE_VS_PLATFORM_NAME variableBrad King2014-09-051-0/+7
|
generated by cgit v0.12 at 2024-11-07 06:20:41 (GMT)