Re: Targetting Tiger

2009-01-24 Thread Clark Cox
On Sat, Jan 24, 2009 at 8:48 AM, Matt Long wrote: > Not sure what you mean by "capable of running tiger". If you have a machine > capable of running Leopard, it should be able to run tiger. Not true. In general, any Mac requires the latest OS available at the time it was released. So machines rel

Re: Targetting Tiger

2009-01-24 Thread Steve Christensen
On Jan 24, 2009, at 11:34 AM, Marcus wrote: 24 jan 2009 kl. 16.56 skrev Steve Christensen: And I'd suggest getting your hands on a 10.4 system of your own, particularly if current or future customers have that as a requirement. My customer does so I'm doing all my development with Xcode 2

Re: Targetting Tiger

2009-01-24 Thread Thomas Davie
On 24 Jan 2009, at 22:17, Steve Christensen wrote: On Jan 24, 2009, at 9:22 AM, Thomas Davie wrote: On 24 Jan 2009, at 17:48, Matt Long wrote: Not sure what you mean by "capable of running tiger". If you have a machine capable of running Leopard, it should be able to run tiger. Fraid not

Re: Targetting Tiger

2009-01-24 Thread Steve Christensen
On Jan 24, 2009, at 9:22 AM, Thomas Davie wrote: On 24 Jan 2009, at 17:48, Matt Long wrote: Not sure what you mean by "capable of running tiger". If you have a machine capable of running Leopard, it should be able to run tiger. Fraid not, the two machines I have available to develop on are to

Re: Targetting Tiger

2009-01-24 Thread Chris Hanson
On Jan 24, 2009, at 8:48 AM, Matt Long wrote: Not sure what you mean by "capable of running tiger". If you have a machine capable of running Leopard, it should be able to run tiger. Macs typically doesn't support operating system releases earlier than the one with which it shipped, because

Re: Targetting Tiger

2009-01-24 Thread John Joyce
Your best bet is to purchase a used Mac that can run Tiger and use it for test builds. There is a huge installed userbase of Tiger still, remember it has been the longest single incarnation of OS X. (as a result of this long life of Tiger, there are lots of affordable used macs that can do

Re: Targetting Tiger

2009-01-24 Thread Marcus
24 jan 2009 kl. 16.56 skrev Steve Christensen: And I'd suggest getting your hands on a 10.4 system of your own, particularly if current or future customers have that as a requirement. My customer does so I'm doing all my development with Xcode 2.5 on a 10.4.11 system. I make sure everythin

Re: Targetting Tiger

2009-01-24 Thread Thomas Davie
On 24 Jan 2009, at 17:48, Matt Long wrote: Not sure what you mean by "capable of running tiger". If you have a machine capable of running Leopard, it should be able to run tiger. Fraid not, the two machines I have available to develop on are too new to run tiger – there's no drivers for them

Re: Targetting Tiger

2009-01-24 Thread Matt Long
Not sure what you mean by "capable of running tiger". If you have a machine capable of running Leopard, it should be able to run tiger. Someone correct me if I'm wrong as I haven't actually done this, but can' t you simply get an external drive you connect through USB and install tiger onto

Re: Targetting Tiger

2009-01-24 Thread David Blanton
I agree with Steve as this is exactly how I develop to be sure 10.4 and 10.5 work. On Jan 24, 2009, at 8:56 AM, Steve Christensen wrote: And I'd suggest getting your hands on a 10.4 system of your own, particularly if current or future customers have that as a requirement. My customer does

Re: Targetting Tiger

2009-01-24 Thread Steve Christensen
Your build settings below look reasonable, but given where the crash is happening it looks like the problem is with your main nib file. Is it possible that it contains a new Leopard-only view class, for example? Does IB show any incompatibilities with your xib or nib with a 10.4 target? A

Targetting Tiger

2009-01-24 Thread Thomas Davie
Hi, I'm in a sticky situation. I personally have no machine capable of running tiger, but my customer needs me to provide a tiger version of my app. I attempted to create a build that targeted tiger, but they are reporting that it is failing. What's going wrong: The application crashes