File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -302,20 +302,20 @@ build nodes for the its `SwiftTargetBuildDescription` and
302
302
303
303
##### Module Maps
304
304
305
- The product module map’s purpose is to define the public API of the mixed
305
+ The client-facing module map’s purpose is to define the public API of the mixed
306
306
language module. It has two parts, a primary module declaration and a secondary
307
307
submodule declaration. The former of which exposes the public C language
308
308
headers and the latter of which exposes the generated interop header.
309
309
310
- There are two cases when creating the product module map:
310
+ There are two cases when creating the client-facing module map:
311
311
- If a custom module map exists in the target, its contents are copied and
312
312
extended to modularize the generated interop header. These contents are
313
313
written to the build directory as ` extended-custom-module.modulemap ` .
314
314
Since the public header directory and build directory are passed as import
315
315
paths to the build invocations, a different name is needed for this module
316
316
map as the ` -import-underlying-module ` should only be able to find one
317
317
` module.modulemap ` file from the given import paths.
318
- - Else, the product module map’s contents will be generated via the same
318
+ - Else, the module map’s contents will be generated via the same
319
319
generation rules established in [ SE-0038] with an added step to generate the
320
320
` .Swift ` submodule. This file is called ` module.modulemap ` and lives in the
321
321
build directory.
You can’t perform that action at this time.
0 commit comments