Universal binary with different deployment targets - how?
Universal binary with different deployment targets - how?
- Subject: Universal binary with different deployment targets - how?
- From: "Roni Music" <email@hidden>
- Date: Sat, 8 Aug 2009 17:40:21 +0200
I've posted this question on the iPhone developer forum but haven't got any
useful replies so I'm trying here:
I've just bought the new iPhone 3GS (which has an arm7 processor) and
decided to
build my app as a fat/universal binary.
So one slice is for the older arm6 processor and the other slice for the
newer
arm7 processor. My app doesn't require any OS 3 features and I still want it
to
run on OS 2 (in my case OS 2.2.1).
I'm using SDK 3, I set the "iPhone OS Deployment Target" to iPhone OS 2.2.1
which then sets "MinimumOSVersion" in the Info.plist file to 2.2.1.
This way my app runs both on my older iPhone 3G with OS 2.2.1 using the arm6
slice and on my newer iPhone 3GS with OS 3 using the arm7 slice.
My app does a lot of DSP processing and being able to compile for the arm7
processor makes it a lot faster. The improvement is dramatic and the
app runs like a charm.
Now when finished and uploading it to the app store, I get an error message
saying:
"The binary you uploaded was invalid. Fat binaries require a
MinimumOSVersion of
at least 3.0".
How can I set the arm7 slice to deployment target 3.0 and the arm6 slice to
deployment target 2.1.1?
I'm not sure if this makes the application acceptable by the iPhone
AppStore, if
not, anyone knows how to do this? After all, the whole idea with fat
binaries is
to target different architectures and OS versions.
Could the LSMinimumSystemVersionByArchitecture setting in the Info.plist
file be
a solution?
Thanks for any advice.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden