Importing multiple swift bindings modulemap collision

[reez]

Describe the bug
When Importing two swift frameworks generated via FFI there is a Build error.

Showing Recent Issues
duplicate output file '/include/module.modulemap' on task: ProcessXCFramework /DerivedData/Build/Products/Debug-iphonesimulator/libbdkffi.a ios simulator

Showing Recent Issues
Multiple commands produce '/Build/Products/Debug-iphonesimulator/include/module.modulemap'

Showing Recent Issues
Command: ProcessXCFramework /Build/Products/Debug-iphonesimulator/libportal.a ios simulator

Showing Recent Issues
Command: ProcessXCFramework /Build/Products/Debug-iphonesimulator/libbdkffi.a ios simulator

To Reproduce
Import bdk-swift and some other swift bindings generated the same way

Expected behavior

Build environment

• BDK tag/commit:
• OS+version:
• Rust/Cargo version:
• Rust/Cargo target:

Additional context

[reez]

Fails using bdk-swift:

• 1.0.0-beta.5
• 1.0.0-beta.2

Succeeds using bdk-swift:

• 0.31.2
• 1.0.0-alpha.11

The other swift bindings I was importing was using uniffi = { version = "0.26.1", optional = true }

[reez]

The other swift bindings I was importing was using uniffi = { version = "0.26.1", optional = true }

I tested bumping the other swift bindings I was importing from 0.26.1 to 0.28.0, to match bdk-swift beta 2+5, and the results were the same...

Fails using bdk-swift:

• 1.0.0-beta.5
• 1.0.0-beta.2

Succeeds using bdk-swift:

• 0.31.2
• 1.0.0-alpha.11

[reez]

I believe I have a fix for this by using a unique subdirectory to prevent collisions. Tested.

This will show up if someone builds their xcframework the same way bdk-ffi does (see our build-xcframework.sh), they will get errors similar to what is seen above.