LiveCode Forums.

Hi all

Really struggling to complete an iOS build after I had some issues with my SDKs. I'm now trying on 3 different versions of LC (7.0.6, 7.1.3, 7.1.4), whereas just a week ago the builds were completing with no issue on 7.0.6 and 7.1.3. I had originally got the error of LC needing the iOS 9.2 SDK which is why I had to shuffle Xcode files around, but now I can't seem to figure out what this new error is after googling and none of the answers working.

On 7.1.4 I receive the error when building:
linking for arm failed with lipo: error: unable to find utility "lipo", not a developer tool or in PATH

On 7.0.6:
linking for arm (arm64) failed with g++: error: unable to find utility "g++", not a developer tool or in PATH

I have tried swapping between different stacks on both versions with the same results, my stacks do not have any externals/substacks and my Externals folder in LC has been emptied out. I have Xcode 6.2 installed and also installed 7.3 afterwards in conjunction.

Do a search on the forum for arm failed. You'll get plenty of information. Probably you need to open Xcode and sign the Ts & Cs.

quailcreek wrote:Do a search on the forum for arm failed. You'll get plenty of information. Probably you need to open Xcode and sign the Ts & Cs.

That's why I mentioned I had looked around already. I tried the T&C's one, didn't work.

I have actually had to uninstall all of my Xcode and Livecode versions simultaneously and then go back to LC 7.0.6 and Xcode 6.2 for anything to work again. Hooray for unsupported SDKs, another reason why I can never reliably update to newer LC versions.

You can keep multiple copies of Xcode and LC on disk. No need to uninstall. Right now I have four versions of LC and three Xcode.

jacque wrote:You can keep multiple copies of Xcode and LC on disk. No need to uninstall. Right now I have four versions of LC and three Xcode.

I did keep 7.0.6 and 7.1.3 as well as Xcode 6.2 and 7 together on disk for a while, and it was all fine until I started getting these errors, and then the only solution seemed to be a clean install of these older versions. I'm not saying your setup wouldn't generally work, just that mine was the only reliable solution to this issue I had.