Closed thii closed 1 year ago
this is arm64_32? zld will probably never link it on its own unless apple chooses to release the source for arm64_32 linking (no idea why they won't)
How does it not fallback to the provided original ld path here?
looking closer, i guess it's not arm64_32, the target says arm64-apple-watchos7.0-simulator
. why would the simulator use arm64? is this a new arm mac? my watchos knowledge is limited
No, it's an Intel Mac. Not a watchOS expert here either, but what I'm seeing is that when you build your parent iOS app for a simulator (x86_64), Xcode builds a universal binary watchOS app that combines two archs x86_64 and arm64.
i thought watchos only used arm64_32 and armv7k, does it also now use arm64?
No idea, I'm guessing that's because the watch simulator on an Apple Silicon would use arm64?
Diffing the build commands, this flag was what makes it fail (it is added when you set ENABLE_BITCODE = YES
in the watch target):
-fembed-bitcode-marker
is this still a problem on latest master?