| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
2eb30a7036 add_subdirectory: Add SYSTEM option
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7399
|
| |
| |
| |
| |
| | |
Fixes: #22401
Signed-off-by: Da Quexian <daquexian566@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replace our hard-coded default for `/Zi` with a first-class abstraction
to select the debug information format an enumeration of logical
names. We've long hesitated to do this because the idea of "debug
information format" touches on related concepts on several platforms.
Avoid that scope creep by simply defining an abstraction that applies
only when targeting the MSVC ABI on Windows.
Removing the old default flag requires a policy because existing
projects may rely on string processing to edit them and choose a
runtime library under the old behavior. Add policy CMP0141 to
provide compatibility.
Fixes: #10189
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
f808d8afb9 CMake: Support upcoming C++26 language level
Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Raul Tambre <raul@tambre.ee>
Merge-request: !7601
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
36400e9dc1 COMPILER_LAUNCHER: Add support for generator expressions
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7613
|
| |/ /
| | |
| | |
| | | |
Fixes: #23441
|
| | | |
|
|/ / |
|
| | |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The CMAKE_MSVC_RUNTIME_LIBRARY variable docs mention that it
initializes the MSVC_RUNTIME_LIBRARY target property, but the
property's docs was missing any mention of the variable.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
83e44002ae VERIFY_INTERFACE_HEADER_SETS: Add verification target for all
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7536
|
| | |
| | |
| | |
| | | |
Fixes: #23802
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
c31f9ef22b Help: Document initialization of VERIFY_INTERFACE_HEADER_SETS property
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7528
|
| | |
| | |
| | |
| | |
| | | |
The docs for the CMAKE_VERIFY_INTERFACE_HEADER_SETS variable do
mention that it initializes the property, but the property docs didn't
mention the variable. Add that missing cross-reference.
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
into release-3.24
41f15193e5 VERIFY_INTERFACE_HEADER_SETS: Fall back to global languages
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7517
|
|\ \ \ \
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
41f15193e5 VERIFY_INTERFACE_HEADER_SETS: Fall back to global languages
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7517
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If a target doesn't have any source files, fall back to the global
list of enabled languages to determine the language of the header
file to verify.
Fixes: #23774
|
|\ \ \ \
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
f5dd1817d1 Help: Clarify that VERIFY_INTERFACE_HEADER_SETS supports interface libraries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7507
|
| |/ / |
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
f585c61667 Help: LINK_LIBRARIES_ONLY_TARGETS also checks injected direct libraries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7466
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The INTERFACE_LINK_LIBRARIES_DIRECT property can add direct
link dependencies to the target at the head of the dependency chain.
The checks associated with LINK_LIBRARIES_ONLY_TARGETS also apply
to these link items, but the documentation wasn't updated to reflect
this when the INTERFACE_LINK_LIBRARIES_DIRECT support was added.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
6b103dd58a Help: Fix wrong property name INTERFACE_PROPERTY_LINK_DIRECT
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7461
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is the name of a placeholder used for some documentation in
`Help/prop_tgt/INTERFACE_LINK_LIBRARIES_DIRECT.txt` that is included in
multiple documents. During development iterations, much of the content
was moved to just `Help/prop_tgt/INTERFACE_LINK_LIBRARIES_DIRECT.rst`,
but the placeholder was not correctly replaced by its property name.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
703900d166 Help: Mention CMP0131 in LINK_LIBRARIES docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7444
|
| | | |
|
|\ \ \
| |/ /
| | /
| |/
|/|
| |
| | |
d185f7c0a8 Help: Rework $<LINK_LIBRARY>, $<LINK_GROUP> and related docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7413
|
| |
| |
| |
| |
| |
| |
| | |
These changes restructure the docs to improve readability and flow,
correct grammar and typos, and fix errors and inconsistencies in
some of the examples.
Fixes: #23684
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
9a0a94fdaa VS: Add variable to to turn off Visual Studio compile batching
a7ebb73929 Help: Improve formatting in VS_NO_COMPILE_BATCHING docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !7405
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Extend the change from commit b764c7c273 (VS: Add property to turn off
Visual Studio compile batching, 2022-02-07, v3.24.0-rc1~710^2) by
adding a variable to initialize the property on every target.
Issue: #23179
Fixes: #23639
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
9680b3b279 Add EXPORT_NO_SYSTEM target property, deprecate IMPORTED_NO_SYSTEM
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7379
|
| | |
| | |
| | |
| | |
| | |
| | | |
Issue: #18040
Signed-off-by: Da Quexian <daquexian566@gmail.com>
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
07bc3b07ec gitlab-ci: test C++ modules using GCC
1b2270aa4e ci: add a Docker image to test out C++ modules with GCC
8c5a53096a Tests/RunCMake/CXXModules: add module-using examples
4151547e2f cmGlobalNinjaGenerator: use `cmModuleMapper` implementation
b43bdaff3c cmCxxModuleMapper: implement support for GCC's module map format
02d0f0e752 cmCxxModuleMapper: add source to handle module mapper contents
a046a45aad cmGlobalNinjaGenerator: add a TODO for header units
386465bf83 cmTarget: add support for C++ module fileset types
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7369
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
C++ modules have two variants which are of importance to CMake:
- `CXX_MODULES`: interface modules (those using `export module M;`,
`export module M:part;`, or `module M:internal_part;`)
- `CXX_MODULE_HEADER_UNITS`: importable header units
Creating C++ modules or partitions are *not* supported in any other
source listing. This is because the source files must be installed (so
their scope matters), but not part of usage requirements (what it means
for a module source to be injected into a consumer is not clear at this
moment). Due to the way `FILE_SET` works with scopes, they are a perfect
fit as long as `INTERFACE` is not allowed (which it is not).
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
69beee5314 Add SYSTEM target property
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7308
|
| |/
| |
| |
| |
| |
| |
| |
| | |
If it is ON, treat INTERFACE_INCLUDE_DIRECTORIES as system include directories.
Issue: #18040
Signed-off-by: Da Quexian <daquexian566@gmail.com>
|
|/ |
|
|
|
| |
Fixes: #22405
|
|
|
|
|
|
|
|
| |
Add a new property, INTERFACE_HEADER_SETS_TO_VERIFY, which contains
a list of header sets that should be verified by
VERIFY_INTERFACE_HEADER_SETS.
Fixes: #23522
|
|
|
|
| |
Issue: #23448
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
76a08cd253 COMPILE_WARNING_AS_ERROR: Add options to treat warnings as errors
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Acked-by: Michael Hirsch <michael@scivision.dev>
Merge-request: !7187
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add `COMPILE_WARNING_AS_ERROR` target property and supporting
`CMAKE_COMPILE_WARNING_AS_ERROR` variable.
`COMPILE_WARNING_AS_ERROR` is initialized by
`CMAKE_COMPILE_WARNING_AS_ERROR`. It is a boolean variable. If it is
true, it expands to a different flag depending on the compiler such that
any warnings at compile will be treated as errors.
Supports compiler ids that I could find a relevant flag for.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add a `CMAKE_WATCOM_RUNTIME_LIBRARY` variable to control the
runtime library selection. Add policy CMP0136 to switch to
in place of the old hard-coded default flags.
Fixes: #23178
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
d89af11f89 VS: Add StartupObject property for managed .NET projects
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7171
|
| |/ |
|