Re: long Tigers
Re: long Tigers
- Subject: Re: long Tigers
- From: "Gerriet M. Denkmann" <email@hidden>
- Date: Sat, 14 May 2005 00:02:26 +0200
On 13.05.2005, at 22:34, j o a r wrote:
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.
There are 3 cases:
1. Compiling on Tiger or Panther
the only way to check for this I know of is:
#ifdef __HFS_FORMAT__
#warning This is being compiled on Tiger or later
#else
#warning Panther or earlier
#endif
But I would like to have something less hackish.
I need this, because quite a lot of include things have changed in
Tiger.
I have 2 computers: one TIger and one Panther, and I like to use both.
2. Running on Tiger or Panther
Here I use: Gestalt( gestaltSystemVersion, &vers)
This I need because many things work differently on my 2 computers.
3. Using Tiger only stuff (e.g. Core Data)
In this case one needs to weak link and supply work-arounds if the app
is running on a pre-Tiger system.
But this is not my problem.
Do you really need to compile on Panther?
Yes. As long as I have two different OS versions. And I will keep
Panther until all my apps work on Tiger.
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...
Yes, had some minor problems with this - but nothing really bad.
Gerriet.
_______________________________________________
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