I have seen a few projects where there is a import Module and a import Module.Internal.
If I open them up and build them I can see that the built .framework file in the Modules/ folder has both module.modulemap and module.private.modulemap. As expected module.private.modulemap starts off with explicit module AdobeCreativeSDKCore.Internal {
I am guessing that if I wanted to set things up so that both modulemaps were exported in build settings I would set the private modulemap to the module.private.modulemap file essentially.
Whats confusing to me is in one example they did this in a swift package. And they did this where the xcframework is imported via a simple .linkedFramework("Module", .when(platforms: [.iOS])) statement within linkerSettings. What I cant see is how they are getting it to work such that code within that swift package can import both Module and Module.Internal. Frankly I cant really even tell what that linkedFramework statement is linking to. Module is not a dependency. There is literally a Module and I do not know how it gets there or how Swift packages is smart enough to see it and be able to pull in both modules. But categorically per this comment I thought it was impossible to use a private module map like this in a Swift Package?
