Re: long Tigers
Re: long Tigers
- Subject: Re: long Tigers
- From: j o a r <email@hidden>
- Date: Fri, 13 May 2005 22:34:48 +0200
On 13 maj 2005, at 20.41, Gerriet M. Denkmann wrote:
Yes, I did look at AvailabilityMacros. But still I do not know what
to use.
#ifdef What_to_insert_here?
#warning This is being compiled on Tiger or later
#else
#warning Panther or earlier
#endif
You're talking about compiling *on* Tiger or Panther, not *for* Tiger
or Panther. In many cases it's more important to consider the target
OS for your binary, and that's where the Cross Development SDK and
the availability macros might be able to assist you. Using the SDK
you can compile *on* Tiger *for* both Panther and Tiger. While that
might be helpful in many cases, it might not be what you're looking
for. In that case you can probably stop reading now...
I always use the SDK for my projects. I think that there is little
reason not to, and it adds a lot of value. Read the docs to learn how
to use this functionality, but basically you use Xcode to set your
system library root and MACOSX_DEPLOYMENT_TARGET, which in turn among
other things determines the MAC_OS_X_VERSION_MIN_REQUIRED. In your
code you can then do:
#if MAC_OS_X_VERSION_MIN_REQUIRED > MAC_OS_X_VERSION_10_3
// Stuff for Tiger
#ele
// Stuff for earlier versions
#endif
Do you really need to compile on Panther? If you do, another problem
is of course that there is no version of Xcode that runs on both
Panther and Tiger, and while the project files are mostly portable
between the latest versions, it might not be for the faint of heart...
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden