Re: Building For OS 10.1, 10.2, and 10.3
Re: Building For OS 10.1, 10.2, and 10.3
- Subject: Re: Building For OS 10.1, 10.2, and 10.3
- From: Glen Low <email@hidden>
- Date: Tue, 6 Jan 2004 07:44:26 +0800
Chris:
If you want to build something on the current OS but make sure it runs
on older OS versions, you only need to set the Mac OS X Deployment
Target setting. This ensures that any APIs that you use that are
newer than that target are "weak-linked", that is, do not cause
load-time failures but are instead set to null. You need to check for
null before calling any API that was introduced after your target
(this includes later versions of that target: if you set your target
to 10.2, you may need to check for APIs introduced in 10.2.110.2.8 as
well as those introduced in 10.3.x)
You do not need to change the SDK setting from "Current" if all you
want to do is to run on older versions.
If you don't want to do the runtime checks for APIs, and you're not
using new Panther features, you can set the SDK to an older version
(10.2.8, for example). If you use 10.3.x constructs, you'll get a
compiler error or warning. Your code will run on 10.2 through 10.3.x.
What then is the implication of having External Frameworks and
Libraries pointing to frameworks in the main system and not to the SDK?
Does setting the cross-develop target (project info) and/or deployment
target (target build info) cause these to automagically refer to their
counterparts in the SDK?
Cheers, Glen Low
---
pixelglow software | simply brilliant stuff
www.pixelglow.com
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.