| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This is needed to support `add_test(NAME)` tests in KWSys.
|
|\
| |
| |
| |
| |
| |
| | |
54e376df2e Help: Update link to Qt 5 CMake docs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8751
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
d562e503aa libuv: Use SIGCHLD in bootstrap mode
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8748
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
439722993e CMakeLibTests: Compile with WIN32_LEAN_AND_MEAN
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8750
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
d2c30ac063 Help:CheckCXXSymbolExists: refer to CheckSourceCompiles
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8746
|
| | |
| | |
| | |
| | | |
This was just missed in the earlier MR.
|
| | | |
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
a1509658a0 ExternalProject: Ensure svn --trust-server-cert has dependent options
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8745
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the --trust-server-cert option is given to svn without the
--non-interactive option, the command fails with an error.
Previously, --non-interactive was always added, but
b1c2cb0436a (ExternalProject: Make SVN interactive with
USES_TERMINAL_{DOWNLOAD,UPDATE}, 2022-05-06) changed
the behavior to only add it if the relevant USES_TERMINAL_...
option was set to true.
Fixes: #25197
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
48ee946fdc cmExperimental: recycle the C++ modules API UUID
1a1806a71b gitlab-ci: declare `bmionly` support for modules where possible
457a12f3f9 Tests/RunCMake/CXXModules: add tests which use modules from imported targets
9b9ec70b54 Ninja: generate scanning and build rules for C++20 module synthetic targets
80ef50a191 CXXModules: add a variable for BMI-only compilation
80d6544398 cxxmodules: generate synthetic targets as an initial pass
3dc6676ecc cmSyntheticTargetCache: add a struct for synthetic target caching
cb356b540c cmCxxModuleUsageEffects: add a class to capture module usage effects
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8535
|
| | | |
| | | |
| | | |
| | | | |
Supporting modules on IMPORTED targets is worth an update.
|
| | | |
| | | |
| | | |
| | | | |
GCC and Clang both have the settings.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This will be required when dealing with imported targets which contain
modules.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We need to be able to construct BMIs that will be usable from the client
modules for the target importing the module, so create BMI-only
compilation rules for `IMPORTED` targets to create these BMIs.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When importing a C++ module, there may be requirements imposed by the
importer so that the compiler can reliably read the BMI. For example,
the standard used in the importer may need to also apply to the imported
BMI.
Right now, there are no tracked requirements. As we learn more, this
class can start tracking more information.
See: https://wg21.link/p2581r2
|
| | | |
| | | |
| | | |
| | | | |
This avoids invalid states from existing.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The collator needs to know that the object *is* a BMI so that it can
just use the location directly.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
It will also be used to copy from other targets, not just directories.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
While not "usage requirements" directly, when applied to a target that
will eventually have the BMI compile rules attached to them, they need
tracked as such.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When consuming exported targets which contain C++ modules, the consuming
project must be able to recompile BMI files using the original target's
flags. This is because a module source may use some private target usage
requirement but not want to propagate it to consumers. To facilitate
this, export the private information as necessary for consumers to be
able to perform the BMI compilations.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Some callers have their own error reporting mechanisms which give more
context. Support handing off the error string for these use cases.
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
741755f637 Help: Document cmake_minimum_required deprecation of old versions
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: scivision <michael@scivision.dev>
Merge-request: !8742
|
|\ \ \ \ \ \
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
741755f637 Help: Document cmake_minimum_required deprecation of old versions
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: scivision <michael@scivision.dev>
Merge-request: !8742
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Document the deprecation warnings added by commit 5845c218d7 (Deprecate
compatibility with CMake versions older than 2.8.12, 2020-06-12,
v3.19.0-rc1~629^2) and commit 3a4791548d (Deprecate compatibility with
CMake versions older than 3.5, 2023-02-09, v3.27.0-rc1~508^2).
Fixes: #25196
|
| |_|_|/ /
|/| | | | |
|
| | | | | |
|
|\ \ \ \ \
| | |/ / /
| |/| | | |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
1140087ade LLVMFlang-Fortran: Add flags for build types
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8741
|
|\ \ \ \ \ \
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
1140087ade LLVMFlang-Fortran: Add flags for build types
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8741
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
Fixes: #25193
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
8b1257e7bf Debugger: Replace libuv with platform-specific connection code
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8711
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove libuv usage from CMake debugger. Libuv has an async io model
and cppdap uses a sync model, so an extra thread and a buffer copy
were necessary to match semantics. In order to eliminate those
costs this commit implements the IO using platform specific APIs.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
7d3f4e12d2 Tutorial: Clarify instructions for multi-config generators in Step 1
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8734
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
a8634b878a Help:ENV: note escaping needed for special characters
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8733
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
eee1dc10be libuv: Compile as C11 on all Solaris versions
d6b4f6dd97 libuv: Remove unused compatibility code for CMake < 3.9
5fb17a1410 libuv: win,spawn: allow %PATH% to be unset
703e3e03c3 libuv: Comment why we cannot update past 1.44.2
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8744
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Using `_XOPEN_SOURCE=600` on Solaris 5.10, as we do on Solaris 5.11+
already, allows the system headers to be included in C99 and C11 modes.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We now require CMake 3.13 or higher anyway.
|