| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes: #20178
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
557ea4614e VS: Change CMAKE_VS_WINRT_BY_DEFAULT to not implicitly enable WinRT
7bcef355bf Vs: Add test for VS_WINRT_BY_DEFAULT
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4127
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Original behaviour would unconditionally enable WinRT for all projects
so source file flag generation code can acknowledge WinRT being present
and disable it for C language source files. An unintentional result of
that approach is that WinRT is enabled for ALL projects, including C++
projects/source files with no way to disable it
Instead use `CMAKE_VS_WINRT_BY_DEFAULT` as a hint that the platform is
WinRT-by-default and set global `CompileAsWinRT` flag to `false` unless
it was explicitly requested by either `WINRT_COMPONENT` option or `/ZW`
compilation option - similar to what Windows Phone/Windows Store
platform logic does
In case WinRT compilation is enabled for a project by either of
aforementioned methods, C language source file override logic will still
kick in and disable CompileAsWinRT for C source files
Fixes: #20063
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
24fdd51f45 Refactor: Replace CMAKE_CURRENT_LIST_DIR with CMAKE_CURRENT_FUNCTION_LIST_DIR
90e3e2a777 cmFunctionCommand: Introduce `CMAKE_CURRENT_FUNCTION*` variables
dd54290dab Refactor: Modernize `function` command
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !4000
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`CMAKE_CURRENT_FUNCTION`
Can be used for diagnostic or debugging messages like the
`__PRETTY_FUNCTION__` macro of GCC.
`CMAKE_CURRENT_FUNCTION_LIST_DIR`
Eliminates the necessity of the additional "global"
variables inside a module used to access additional "resource"
files from functions defined in the module.
...
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
2467a2b318 CUDA: Add cuda meta-features (e.g. ``cuda_std_11``) support
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3992
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
676befdf52 ctest: add support for memcheck using Dr. Memory
2db0a65f56 cmCTestMemCheckHandler.cxx: minor refactoring
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4119
|
| | | |
| | | |
| | | |
| | | | |
Fixes: #19788
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
e6f758be6d ctest: Populate CTEST_CONFIGURATION_TYPE from the -C command line when set
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4109
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
6f48c59257 launcher: support setting a compiler launcher through the environment
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4095
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
This makes it much easier to use a launcher for all CMake projects in an
environment rather than having to remember to pass the setting to every
CMake build.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
fb4a39a900 Help: Clarify INSTALL_RPATH_USE_LINK_PATH documentation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4108
|
| |/ /
| | |
| | |
| | |
| | | |
State explicitly that directories containing linked library files
are also included even if they are not in the linker search path.
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Currently the document says that `CMAKE_HOST_SYSTEM_PROCESSOR` is the
output of `uname -p` if a system supports `uname`. Update the
documented behavior to match `CMakeDetermineSystem.cmake` code.
Fixes: #20004
|
| |
| |
| |
| | |
Closes: #19967
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
665954fa8d ObjC: Document ObjC/ObjCXX standard properties / variables
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4031
|
| | |
| | |
| | |
| | | |
Fixes: #19919
|
|\ \ \
| |/ /
| | /
| |/
|/|
| |
| | |
fcacd8ce8d Help: Improve readability and fix inaccuracies in unity build docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4019
|
| | |
|
| |\
| | |
| | |
| | | |
Merge-request: !3985
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
dd05ef429a Help: Fix inaccuracies in INSTALL_REMOVE_ENVIRONMENT_RPATH docs
ac8de0dbcf RPATH: Remove stray indent in generated file(RPATH_CHANGE) command
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3985
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The previous docs assumed one had to set INSTALL_RPATH for
this target property to have an effect, but the actual condition is
only that the install rpath is different to the build rpath. Even if
the install rpath is empty, it is possible that CMake will rewrite
the rpath during install because the build rpath could be
non-empty.
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
55df3954d3 find_package: Add support for CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3968
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Extend the change from commit 1d00ba9ccf (Find: find_package prefers
variable CMAKE_FIND_USE_REGISTRY, 2018-11-13, v3.16.0-rc1~461^2~1)
to cover the system package registry too.
Fixes: #19890
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
a0a7a45dbc Help: Fix markup errors, improve wording of CMAKE_FIND... variable docs
049dbdd38c Help: Document that <PackageName>_ROOT applies to config packages too
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3952
|
| | |
|
| |\
| | |
| | |
| | | |
Merge-request: !3919
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f0005dacde Xcode: Add CMAKE_XCODE_SCHEME_ENVIRONMENT variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3933
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Initialize the `XCODE_SCHEME_ENVIRONMENT` target property.
This was left out of commit 6b7f1e1db0 (Xcode: Add variables and
properties to configure schemes, 2018-07-29, v3.13.0-rc1~243^2).
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
f7acc1266c project: Add variable CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE_BEFORE
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3936
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Follow up commit 0761186949 (project: Add variable
CMAKE_PROJECT_INCLUDE_BEFORE, 2019-03-28, v3.15.0-rc1~294^2) with a
project-specific variant. This variable will be used similar to the
already existing `CMAKE_PROJECT_INCLUDE_BEFORE` and
`CMAKE_PROJECT_<PROJECT-NAME>_INCLUDE` variables.
Fixes: #19854
|
| | | |
| | | |
| | | |
| | | | |
Fixes: #18386
|
|/ / /
| | |
| | |
| | | |
Fixes: #19708
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
fb16e0e7c0 Help: Clarify documentation of CMAKE_STATIC_LINKER_FLAGS
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3919
|
| | |
| | |
| | |
| | | |
Issue: #19838
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
7cf79f4419 message: Support logging a context with each message
5bf85e2517 message: Add new CMAKE_MESSAGE_LOG_LEVEL variable
aa59badd6f Tests: Message log level tests must fail on unwanted output
7c579f0a03 Help: Move CMAKE_MESSAGE_INDENT variable to correct section
4b021bd3e9 message: Minor refactor to make code less verbose
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3680
|
| | | |
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
These two options currently do not work well together. Mention this
limitation in the documentation.
Issue: #19826
|
|/ |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
67f3dda69b Help: Document VS 2019 toolset in MSVC_TOOLSET_VERSION
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3841
|
| | |
|
| |\
| | |
| | |
| | | |
Merge-request: !3573
|
| | |
| | |
| | |
| | |
| | | |
Query the number of logical CPUs available to enable parallel
compilation for Swift.
|
| | | |
|