| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
There is an inadvertent inconsistency in the notice for the CPS export
experimental feature as compared to other experimental feature notices.
Change it to be consistent.
|
|
|
|
|
|
|
|
| |
When using the WindowsKernelModeDriver, do not add the new paths
if the variable was not previously defined. Instead, append them
to the existing value.
Add a new GUID for the Experimental mode gate
|
|\
| |
| |
| |
| |
| |
| | |
b151bcfc9e WindowsKernelModeDriver: Add WDK include and link paths on MSVC
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !9705
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Detect Windows Kernel-Mode Driver include directories and library search
paths from the WDK command-line environment. Require toolchain files to
specify the KMDF target version via a new variable.
Since this changes the behavior of the WindowsKernelModeDriver
experimental feature, update its UUID.
|
|/
|
|
|
| |
Given that the feature currently only supports C++ sources and is not
formally accepted by ISO yet, gate it behind a flag.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add initial support for exporting (install only, for now) Common Package
Specification (https://cps-org.github.io/cps/) format package
descriptions. This has some limitations, such as not supporting
generator expressions (as these cannot be portably exported), and only
partially supporting transitive dependencies, but should be usable for
at least some simple cases. (Actually, $<LINK_ONLY> is theoretically
supportable, but is not yet implemented.)
This still needs tests; these will be added in the next commit. Other
potential improvements include support for language-specific compile
definitions and inferring some package properties from project
properties. Additionally, there is no module support yet; this is partly
pending on having a tool agnostic format for providing the necessary
information.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Some design concerns have been raised after trying the 3.29 release
candidates. Avoid committing to a stable public interface for now.
Issue: #25767
|
|
|
|
|
|
|
| |
All the major compilers now have scheduled releases with support for
scanning, so remove the experimental gate.
Fixes: #18355
|
|
|
|
| |
Supporting modules on IMPORTED targets is worth an update.
|
|
|
|
| |
`try_compile` and `try_run` now support C++ modules.
|
|
|
|
|
| |
Other variables may be needed to make experimental features actually
work. List them with the experimental flag.
|
|
|
|
|
| |
ABI checks never use modules, so don't forward the experimental status
through.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The transitive support for Clang is a change in support for the
ecosystem.
|
|
|
|
|
| |
Syntactic support for C++ header units has been removed, so a new UUID
is warranted.
|
|
|
|
|
|
|
|
|
|
| |
These patches now support the `-MF` output, so remove the `none` support
added just for the old patchset which did not use it.
Also update the flag name to `-fmodule-output=`.
Due to the new Clang module mapper flag, use a new experimental support
UUID as well.
|
|
|
|
| |
Visual Studio support warrants a new ID.
|
|
|
|
| |
The set of features available has been expanded, so update the UUID.
|
| |
|
|
|