| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Also add tests.
Fixes: #25828
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When a target uses objects from another target which provides modules as
sources, the modules provided by the referenced target must also be
treated as if they were provided by the referencing target. Add the
concept of "forwarding" modules so that consumers can use modules
created by these sources as well.
Note that this is only sensible for Fortran where module usages are
implicit as far as CMake's visibility model is concerned. C++ modules
have their own concept of visibility which does not require or support
such `$<TARGET_OBJECTS>` reuse in this way.
|
| | |
|
| |
|
|
| |
Missed because the test script did not properly bubble up error reports.
|
| | |
|
| |
|
|
|
| |
The collator will use this to know where the target's export information
needs to go so that module properties may be provided.
|
|
|
The collator will use this to generate property settings for the
imported targets in the build and install export sets.
|
