Xcode 12 beta 3 - error compiling for Simulator

Question

Created Jul ’20

Replies 4

Boosts 0

Views 6.4k

Participants 2

An existing framework library workspace compiles without error when targeting iOS device architecture, but when targeting Simulator I receive the following error:

Code Block in /Users/chris/Downloads/Xcode-beta 3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/lib/darwin/libclang_rt.ios.a(floatditf.c.o), building for iOS Simulator, but linking in object file (/Users/chris/Downloads/Xcode-beta 3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/lib/darwin/libclang_rt.ios.a(floatditf.c.o)) built for iOS, file '/Users/chris/Downloads/Xcode-beta 3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/lib/darwin/libclang_rt.ios.a' for architecture arm64

As this error is referencing platform code I suspect there is some flaw in the Xcode beta (I didn't have this issue with beta 2).

Has anyone else seen this?

Answered by Vertifi in 623154022

SOLVED. I was able to resolve this issue by changing build setting "Build Active Architecture Only" from No to Yes. Hope this helps anyone else that might run into this.

Boost

Answer 1

lmDeveloper1 OP

Jul ’20

i get a simliar build warning for my watch os app,

Building for watchOS Simulator, but linking in object file (/Applications/Xcode-beta.app/Contents/Developer/Platforms/WatchSimulator.platform/Developer/SDKs/WatchSimulator7.0.sdk/usr/lib/libWKExtensionMainLegacy.a(WKExtensionMainLegacy.o)) built for watchOS

sounds like its a xcode / sdk warning, i would create a FB for it, i created one for watchos

0

Answer 2

Vertifi OP

Jul ’20

In my case I'm getting an Error not a warning, and the target is not built. I've also filed a bug report FB8116526. Thanks

0

Answer 3

lmDeveloper1 OP

Jul ’20

oh yeah a error is more serious, but yeah i just get a warning, kinda odd, seems like a xcode / sdk issue for sure.

my FB:

FB8114253

0

Answer 4

Vertifi OP

Jul ’20

Accepted Answer

SOLVED. I was able to resolve this issue by changing build setting "Build Active Architecture Only" from No to Yes. Hope this helps anyone else that might run into this.

0