Paul Woitaschek
12/08/2020, 7:41 AMBoth watchos-armv7k and watchos-arm64_32 represent two equivalent library definitions.
We're building the framework like this:
xcodebuild -create-xcframework \
-framework ios/build/xcode-frameworks/iosArm64/SharedCode.framework \
-framework ios/build/xcode-frameworks/iosX64/SharedCode.framework \
-framework ios/build/xcode-frameworks/watchosArm64/SharedCode.framework \
-framework ios/build/xcode-frameworks/watchosX86/SharedCode.framework \
-framework ios/build/xcode-frameworks/watchosArm32/SharedCode.framework \
-output "$XCFRAMEWORK_DESTINATION_DIR"/SharedCode.xcframework
Did someone manage to get arm32 and arm64 working together for kotlin native on ios / watchos?louiscad
12/08/2020, 7:52 AMKai Limadjaja
12/08/2020, 7:57 AMlouiscad
12/08/2020, 8:10 AMKai Limadjaja
12/08/2020, 8:15 AMPaul Woitaschek
12/08/2020, 8:30 AMBoth watchos-arm64_32 and watchos-armv7k represent two equivalent library definitions.
sergey.bogolepov
12/08/2020, 9:54 AMPaul Woitaschek
12/08/2020, 9:56 AM./bug.sh
Both watchos-arm64_32 and watchos-armv7k represent two equivalent library definitions.
sergey.bogolepov
12/08/2020, 10:30 AMxcodebuild -create-xcframework
.
What worked for me is creation of a fat framework from watchosArm32
and watchosArm64
and then adding it to xcframework instead of separate ones.
Yeah, it is opposite to xcframework's motivation (moving away from fat frameworks), but there is neither documentation nor official answers on Apple developer forum, so... ¯\_(ツ)_/¯Paul Woitaschek
12/09/2020, 6:06 PMlouiscad
12/11/2021, 3:14 PMPaul Woitaschek
12/11/2021, 3:17 PMlouiscad
12/11/2021, 3:18 PMPaul Woitaschek
12/11/2021, 3:19 PMlouiscad
12/11/2021, 3:34 PMPaul Woitaschek
12/11/2021, 4:13 PMsergey.bogolepov
12/13/2021, 10:00 AMdo you have any link for an upstream bug?Unfortunately, no.