Does UnIty 3.4.2 still support building with Xoode 3.2.5 SDK 4.2?

Unity Engine
,
1

Could be my problem as I renamed my project and was doing a few other things just after I upgrade to Unity 3.4.2 but … when i do a build, choose replace the project, and then load up Xcode 3.2.5 and do a regular build I get 8000+ errors.
My project settings remain iPhone+iPad, armv6, iOS latest for SDK target iIOS version is 3.1.3.
The resulting Xcode project shows SDK as latest (currently 4.2)

I noticed that something is now inserting this setting in my build options
setenv FRAMEWORK_SEARCH_PATHS “"/Users/ibyte/dev/xcode_build_output" /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks”
tried removing it but that didn’t help

The errors that start are like this

/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:528: error: expected initializer before '__AVAILABILITY_INTERNAL__IPHONE_4_3'
In file included from /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:50,
                 from /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6,
                 from /Users/glennjones/src/dev/mpiDevice/matchPointKidzXcodeiDevice/Classes/iPhone_target_Prefix.pch:6:
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFError.h:68: error: expected initializer before '__AVAILABILITY_INTERNAL__IPHONE_5_0'
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFError.h:69: error: expected initializer before '__AVAILABILITY_INTERNAL__IPHONE_5_0'
In file included from /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFStream.h:11,
                 from /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFPropertyList.h:13,
                 from /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:55,
                 from /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6,
                 from /Users/glennjones/src/dev/mpiDevice/matchPointKidzXcodeiDevice/Classes/iPhone_target_Prefix.pch:6:
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFURL.h:487: error: expected initializer before '__AVAILABILITY_INTERNAL__IPHONE_5_0'
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFURL.h:626: error: expected initializer before '__AVAILABILITY_INTERNAL__IPHONE_5_0'
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFURL.h:630: error: expected initializer before '__AVAILABILITY_INTERNAL__IPHONE_5_0'
2

Imho building with SDK 4.2 should still work. Try to run “xcode-select” from Terminal and select appropriate Xcode location as default one.

3

Hi Mantas, being a Xcode 4 newbie and not fully understanding Xcode all that much (enough to get by) I managed to figure out that for some reason Xcode 4 is placing references to some iOS5.0 paths in my project. Once I hunted them all down and changed them to 4.2 things were ok.

I also came across something that was really pissing me off and wasting a lot of time … and that was a Xcode 3 setting for build_output_path (which I hard coded to to a particular directory quite some time ago) kept showing up every time i open any project in Xode4 and tried as I might I could not for the life of me figure out why. I could change it per project after the fact.

Turns out after some research that certain settings are migrated from Xcode3 to XCode4 without any way of changing them afterwards in the GUI and to change them if you have to know where to look in the correct preferences files located in your Library path.

Sigh

iByte