summaryrefslogtreecommitdiffstats
path: root/Help
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'vs-default-build-package'Brad King2016-11-293-0/+16
|\ | | | | | | | | 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-293-0/+16
| | | | | | | | | | Add a `CMAKE_VS_INCLUDE_PACKAGE_TO_DEFAULT_BUILD` variable to control this behavior.
* | Merge topic 'try_compile-honor-CMAKE_WARN_DEPRECATED'Brad King2016-11-291-0/+6
|\ \ | | | | | | | | | | | | 6d604c49 try_compile: Honor CMAKE_WARN_DEPRECATED in test project
| * | try_compile: Honor CMAKE_WARN_DEPRECATED in test projectBrad King2016-11-221-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | This causes the `-Wno-deprecated` option to be honored even inside a `try_compile` test project, which is needed to suppress all deprecation warnings as the option documents. Closes: #16446
* | | Merge topic 'initial_cuda_language_support'Brad King2016-11-293-0/+20
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4cc601f2 Help: Add release note for CUDA support 7b9131da CUDA: Add tests to verify CUDA compiler works properly. 9cf5b98d CUDA: Prefer environment variables CUDACXX and CUDAHOSTCXX. a5e806b3 CUDA: Add support for CMAKE_CUDA_COMPILE_OPTIONS_VISIBILITY d038559e CUDA: Add separable compilation support to the makefile generator. 43ce4414 CUDA: Add separable compilation support to the ninja generator. 4b316097 CUDA: Add support for the CUDA_SEPARABLE_COMPILATION target property ae05fcc6 CUDA: Add LinkLineComputer that computes cuda dlink lines. 115269a8 CUDA: Refactor cmLinkLineComputer to allow for better derived children. 5dec4031 CUDA: Refactor CMakeCUDAInformation to prepare for separable compilation. 5b20d0ab CUDA: C++ compile features now enable cuda c++11 support. 489c52ce CUDA: Use the host compiler for linking CUDA executables and shared libs. bbaf2434 CUDA: add support for specifying an explicit host compiler. a92f8d96 CUDA: Enable header dependency scanning. ec6ce623 CUDA: State that cuda has preprocessor output and can generate assembly. 4f5155f6 CUDA: We now properly perform CUDA compiler identification. ...
| * | Help: Add release note for CUDA supportBrad King2016-11-141-0/+6
| | |
| * | CUDA: Add support for the CUDA_SEPARABLE_COMPILATION target propertyRobert Maynard2016-11-142-0/+14
| | |
* | | Merge topic 'imported-interface-no-system'Brad King2016-11-222-0/+6
|\ \ \ | | | | | | | | | | | | | | | | 46005251 Allow NO_SYSTEM_FROM_IMPORTED on imported INTERFACE libraries
| * | | Allow NO_SYSTEM_FROM_IMPORTED on imported INTERFACE librariesBrad King2016-11-212-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Imported INTERFACE libraries can specify include directories via `INTERFACE_INCLUDE_DIRECTORIES` so the default behavior of treating them as system include directories applies. Allow users to turn this off by setting `NO_SYSTEM_FROM_IMPORTED` on such targets. Closes: #16443
* | | | Merge topic 'doc-CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT'Brad King2016-11-223-0/+17
|\ \ \ \ | |/ / / |/| | | | | | | | | | | df9fea7f Help: Document CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT variable
| * | | Help: Document CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT variableBrad King2016-11-213-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | This variable documentation was simply missing. Suggested-by: Craig Scott <craig.scott@crascit.com>
* | | | Help: Mention IMPORTED_LIBNAME_* in interface library property whitelistBrad King2016-11-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | This property was added by commit 09cda9d5 (Allow imported INTERFACE libraries to specify a link library name, 2016-11-03) and is in the implementation's whitelist. Add it to the documentation too.
* | | | Merge topic 'capture-clang-tidy-errors'Brad King2016-11-211-0/+6
|\ \ \ \ | |_|_|/ |/| | | | | | | | | | | | | | | | | | | 80ebc55a cmake: Report if the <LANG>_CLANG_TIDY tool exits with non-zero ce1abfa4 cmake: If ldd for LINK_WHAT_YOU_USE fails to run then report why 44de6157 cmake: Comment why we ignore the include-what-you-use return code
| * | | cmake: Report if the <LANG>_CLANG_TIDY tool exits with non-zeroBrad King2016-11-181-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When using `<LANG>_CLANG_TIDY` our internal launcher for the tool must capture its return code and stderr and report them on failure. Otherwise incorrect command lines silently fail. Closes: #16435
* | | | Merge topic 'backport-android-info-variables'Brad King2016-11-181-15/+0
|\ \ \ \ | |/ / / |/| | | | | | | | | | | 78db7090 Help: Drop release notes for backported Android variables
| * | | Help: Drop release notes for backported Android variablesBrad King2016-11-181-15/+0
| | | | | | | | | | | | | | | | | | | | These do not need to be called out in the 3.7 release notes because they are part of the new Android support feature already covered.
| * | | Android: Add CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINEBrad King2016-11-185-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-183-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * | | Android: Always set CMAKE_ANDROID_NDK_TOOLCHAIN_VERSIONBrad King2016-11-183-1/+10
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | When this variable is not set by the user or toolchain file, set it to the default selected. This will be useful for client code that needs to pass the value to an external tool that needs to find the same toolchain in the NDK. Leave it empty for a standalone toolchain. Suggested-by: Ruslan Baratov <ruslan_baratov@yahoo.com>
| * | Merge branch 'doc-cmake-qt-fixes' into releaseBrad King2016-11-021-1/+1
| |\ \
| | * | Help: Update example Qt 5 find_package call to add missing componentThiago M. de C. Marques2016-11-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Running CMake on it caused the following error: error: Target "publisher" links to target "Qt5::DBus" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? Add the missing DBus component.
| | * | Help: Update example Qt 5 find_package call to use COMPONENTSMarcus D. Hanwell2016-11-021-1/+1
| | | |
* | | | Merge topic 'android-info-variables'Brad King2016-11-178-3/+40
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | f7c5e970 Android: Add CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE d95e6dff Android: Add CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG variable 3d42a72b Android: Always set CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION
| * | | | Android: Add CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINEBrad King2016-11-145-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-143-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * | | | Android: Always set CMAKE_ANDROID_NDK_TOOLCHAIN_VERSIONBrad King2016-11-143-1/+10
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When this variable is not set by the user or toolchain file, set it to the default selected. This will be useful for client code that needs to pass the value to an external tool that needs to find the same toolchain in the NDK. Leave it empty for a standalone toolchain. Suggested-by: Ruslan Baratov <ruslan_baratov@yahoo.com>
* | | | Merge topic 'add-SHA-3'Brad King2016-11-153-6/+35
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | f636d1e7 Help: Add notes for topic 'add-SHA-3' cb5dba8e Tests: Add SHA-3 algorithm coverage to CPack checksum test a9fa6099 ExternalProject: Add support for SHA-3 algorithms b4ffd26f ExternalData: Add support for SHA-3 algorithms 60939702 file: Add support for SHA-3 algorithms 92f95aed string: Add support for SHA-3 algorithms c326209f cmCryptoHash: Add support for SHA-3 algorithms 979e8ba6 Help: De-duplicate and spell out supported hash algorithms 7a79f7e3 librhash: Activate SHA-3 implementation 87584b5e Merge branch 'upstream-librhash' into add-SHA-3 7fcbd47e librhash 2016-11-06 (de79828d) c50c32a3 librhash: Update import script to add SHA-3 implementation
| * | | Help: Add notes for topic 'add-SHA-3'Brad King2016-11-111-0/+4
| | | |
| * | | string: Add support for SHA-3 algorithmsBrad King2016-11-101-0/+8
| | | |
| * | | Help: De-duplicate and spell out supported hash algorithmsBrad King2016-11-102-6/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Spell out the supported algorithms in a definition list in the `string(<HASH>)` command documentation. Revise the `file(<HASH>)` command and CPack module documentation to reference it instead of duplicating the list.
* | | | Merge topic 'swig_add_library'Brad King2016-11-141-0/+8
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a57e7630 Help: Add notes for topic 'swig_add_library' 013193d0 SwigTest: Update for swig_add_library and add lua example ec1d585c UseSWIG: Do not set PREFIX property for SHARED and STATIC lua libraries 4c5b3c1c UseSWIG: Do not set NO_SONAME property for SHARED and STATIC libraries d0a9d8bb UseSWIG: Add swig_add_library macro.
| * | | | Help: Add notes for topic 'swig_add_library'Brad King2016-11-111-0/+8
| |/ / /
* | | | Merge topic 'vs_targets_file_as_library'Brad King2016-11-112-0/+11
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 883bd34a VS: Treat libraries ending in `.targets` as msbuild imports
| * | | | VS: Treat libraries ending in `.targets` as msbuild importsSoji Yamakawa2016-11-092-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Generate `<Import Project="..." .../>` to import the `.targets` files into `.vcxproj` files. Closes: #16340
* | | | | Merge topic 'fuchsia-platform'Brad King2016-11-111-0/+4
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 3cfad71c Add Fuchsia platform module
| * | | | | Add Fuchsia platform modulePetr Hosek2016-11-091-0/+4
| | |/ / / | |/| | | | | | | | | | | | | | | | | | Fuchsia is a new operating system. This module provides a minimal setup needed to use Fuchsia toolchain.
* | | | | Merge topic 'ctest_memcheck_defect_count'Brad King2016-11-112-1/+12
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 3a523eec ctest_memcheck: Add DEFECT_COUNT option to capture defect count
| * | | | | ctest_memcheck: Add DEFECT_COUNT option to capture defect countBetsy McPhail2016-11-092-1/+12
| | | | | |
* | | | | | ExternalProject: Allow passing config flags to git cloneChristian Fetzer2016-11-091-0/+5
| |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a `GIT_CONFIG` parameter that allows to specify `--config` flags that are passed to the git clone command. This can be used to specify for example `core.autocrlf=true`. The `--config` parameter is supported since Git 1.7.7.
* | | | | Merge topic 'imported-interface-libname'Brad King2016-11-094-0/+39
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 09cda9d5 Allow imported INTERFACE libraries to specify a link library name 1d1f1eeb cmTarget: Refactor GetMappedConfig to choose location property up front 479932fa cmTarget: Add comment clarifying interface library special case 925e4270 cmTarget: Clarify comments in GetMappedConfig
| * | | | | Allow imported INTERFACE libraries to specify a link library nameBrad King2016-11-094-0/+39
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add an `IMPORTED_LIBNAME[_<CONFIG>]` target property to specify a library name to be placed on the link line in place of an interface library since it has no library file of its own. Restrict use of the property to imported `INTERFACE` libraries. This will be particularly useful for find modules that need to provide imported libraries from system SDKs where the full path to the library file is not known. Now such find modules will be able to provide an imported interface library and set `IMPORTED_LIBNAME` to refer to the SDK library by name. Issue: #15267
* | | | | Release text for omitting unsupported tags topicDomen Vrankar2016-11-051-0/+8
| | | | |
* | | | | Merge topic 'vs-flag-order'Brad King2016-11-041-0/+9
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | 4cb5d335 VS: Place source-specific AdditionalOptions after target-wide flags
| * | | | VS: Place source-specific AdditionalOptions after target-wide flagsBrad King2016-11-021-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Flags specified in the `COMPILE_FLAGS` source-file property should be placed after those in target-wide properties so that those on individual source files can override those on the whole target. This is already done by most generators but was not implemented correctly for VS 2010 and above. Closes: #16400
* | | | | Help: Document language standard meta-featuresBrad King2016-11-022-0/+34
| | | | |
* | | | | Features: Add meta-features requesting awareness of a particular standardBrad King2016-11-022-0/+18
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A common use case of `target_compile_features` is simply to specify that the compiler should be run in a mode that is aware of e.g. C++11. Some projects simply specify a particular C++11-only feature to request this. Provide a first-class way to do this by naming features after the corresponding language standard. Record them as always available in the corresponding standard level so that requesting them always ensures that standard (or higher) is used.
* | | | Merge topic 'doc-cmake-qt-missing-dbus'Brad King2016-11-021-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 13bc31aa Help: Update example Qt 5 find_package call to add missing component
| * | | | Help: Update example Qt 5 find_package call to add missing componentThiago M. de C. Marques2016-11-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Running CMake on it caused the following error: error: Target "publisher" links to target "Qt5::DBus" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? Add the missing DBus component.
* | | | | Merge topic 'UseSWIG-SWIG_OUTFILE_DIR'Brad King2016-11-021-0/+6
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | 8444b984 UseSWIG: Add option to specify swig output file directory
| * | | | UseSWIG: Add option to specify swig output file directoryCong Zhang2016-11-011-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `swig` has two output-related options: * `-o <outfile>`: Set name of C/C++ output file to <outfile> * `-outdir <dir>`: Set language-specific files output directory to <dir> We already have `CMAKE_SWIG_OUTDIR` for the latter. Add a new `SWIG_OUTFILE_DIR` option for the former.
generated by cgit v0.12 at 2025-01-21 08:14:29 (GMT)