summaryrefslogtreecommitdiffstats
path: root/Source/cmXcFramework.h
diff options
context:
space:
mode:
authorBen Boeckel <ben.boeckel@kitware.com>2023-11-18 03:53:45 (GMT)
committerBrad King <brad.king@kitware.com>2023-11-23 19:25:09 (GMT)
commitd2fa56772f290c61925a70161c77be5f4334fd77 (patch)
treef049f8a15a723b6a7bb70a8efecfb7e1ab254cb3 /Source/cmXcFramework.h
parent06df59b9308d74b3f8a5eada84cf2402dd22b434 (diff)
downloadCMake-d2fa56772f290c61925a70161c77be5f4334fd77.zip
CMake-d2fa56772f290c61925a70161c77be5f4334fd77.tar.gz
CMake-d2fa56772f290c61925a70161c77be5f4334fd77.tar.bz2
Ninja: support "forwarding" modules from other targets
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.
Diffstat (limited to 'Source/cmXcFramework.h')
0 files changed, 0 insertions, 0 deletions