-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode reports "Multiple commands produce '...DerivedData...Build/Products/Debug/include/module.modulemap'" #243
Comments
I can reproduce a similar error without requiring Setapp. Instead I just create two separate packages using swift-bridge. When I try to include both packages in Xcode project I get error:
Trying to figure out moduleAliases fix, but no luck so far. |
I have fixed the
Instead of hardcoding framework name to RustXcframework.xcframework would it make sense to use a unique name each time based on the name passed into Once I do these things then the
Again this is happening when I use swift-bridge to create two swift packages that wrap rust code, and include them both in the same app. |
I think I found solution and have fully documented at end of README here: https://github.com/jessegrosjean/swift-cargo-problem That example is using I think the boiled down answer is that if your swift package references a framework, that framework needs to have unique name, plus unique internal names for headers, etc. So if you are generating swift packages that use an XCFramework you nee to make all the generated values are unique, otherwise you can't use two of the generated packages in the same app. |
I'm wrapping a rust crate into a swift package using swift-bridge. On own it's working great. I add the generated package to my macOS App, and it works.
I'm having a problem when I also add another package (https://github.com/MacPaw/Setapp-framework) to my app. As soon as I do that I get Xcode error:
Any thoughts on what I need to change to fix this problem?
I have reproduced the problem in an example project here:
https://github.com/jessegrosjean/module-map-error
Thanks,
Jesse
The text was updated successfully, but these errors were encountered: