summaryrefslogtreecommitdiff
path: root/Help/prop_tgt/CXX_MODULE_SETS.rst
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'doc-3.25-relnotes'Brad King2022-10-111-0/+2
|\ | | | | | | | | | | | | | | | | 286a40cb5b Help: Update Sphinx versionadded directives for 3.25 release f93f97d6c2 Help: Organize and revise 3.25 release notes c174ef23f4 Help: Consolidate 3.25 release notes Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7751
| * Help: Update Sphinx versionadded directives for 3.25 releaseBrad King2022-10-071-0/+2
| | | | | | | | | | | | | | | | Run the script: Utilities/Sphinx/update_versions.py --since v3.24.0 --overwrite Manually de-duplicate the directive in FindOpenSP.
* | Help: Minor grammar, typo and formatting cleanupsCraig Scott2022-10-091-2/+2
|/
* cmTarget: add support for C++ module fileset typesBen Boeckel2022-06-161-0/+16
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).