Reputation: 1
I have a very old macOS project that I will be porting and converting to 64 bit but for now I need to compile and debug it in 32 bit mode because it has a complex module that will only run in 32 bit mode. I have a Mojave system set up with Xcode 9.4 and can successfully compile everything 32 bit in Terminal with my personal make scheme. However, when I try to throw a test app into Xcode to debug, compilation fails at the link stage. Xcode ignores my libraries because it insists on building 64 bit and then fails on undefined symbols that reside in them. Yep, they are all 32 bit as that's what I need right now.
So stupid question. How do I configure Xcode 9.4 to stop trying to compile 64 bit and only compile 32 bit ? I am brand new to it. It looks like I have all of my compile flags set properly and I have the macOS Deployment Target set to macOS 10.13.
I can set that target all the way down to macOS 10.6 and the same problem still persists.
What's the trick here gang? Do I need to go with an even older version of Xcode?
I tried to remove "x86_64" from Valid Architectures, leaving only "i386" but doing this causes Xcode to immediately crash with a SIGABRT the very instant that I hit the compile button !
Messing around with the "Architectures" setting causes Xcode to crash as well. There isn't a 32 bit only option available there, BTW.
Upvotes: 0
Views: 336
Reputation: 1
Xcode 9.4/9.4.1 is supposed to be the last version able to build 32 bit apps. Well, it’s NOT. It fails miserably.
I rolled back to Xcode 9.2 and it works perfectly.
So, official reports of Xcode v9.4 as the last 32 bit project builder are incorrect.
If you need to compile and debug old 32 bit code, go with v9.2.
Actually, v9.3.1 works too.
Just stay away from 9.4+ if you need to compile and link 32 bit binaries
Upvotes: 0