Re: Targetting Tiger
Re: Targetting Tiger
- Subject: Re: Targetting Tiger
- From: Matt Long <email@hidden>
- Date: Sat, 24 Jan 2009 09:48:49 -0700
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 it while leaving your current system in tact on the
internal drive?
It's going to be a nightmare to debug the environment if you don't
have a dev environment to match. I've (hate to admit it) tried this
before. It did not work out well and the customer was pretty
frustrated as I was trying to get them to "try" my debug builds and
report back to me. Not one of my brighter moments. ;-)
Seems like getting a tiger system set up shouldn't be too tough. Or am
I way off here?
Best regards,
-Matt
On Jan 24, 2009, at 8:56 AM, Steve Christensen wrote:
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?
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 everything works on 10.4
first, then also make sure that nothing weird happens on 10.5.
steve
On Jan 24, 2009, at 1:44 AM, Thomas Davie wrote:
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 almost immediately (on tiger, but not
leopard) while loading its nib, here's the back trace:
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 libobjc.A.dylib 0x90a594c7 objc_msgSend + 23
1 com.apple.AppKit 0x932639d8 loadNib + 303
2 com.apple.AppKit 0x932633d9 +[NSBundle(NSNibLoading)
_loadNibFile:nameTable:withZone:ownerBundle:] + 918
3 com.apple.AppKit 0x9326303a +[NSBundle(NSNibLoading)
loadNibFile:externalNameTable:withZone:] + 164
4 com.apple.AppKit 0x93262f7c +[NSBundle(NSNibLoading)
loadNibNamed:owner:] + 392
5 com.apple.AppKit 0x93262cc3 NSApplicationMain + 433
6 com.davie.klondike 0x0000237a _start + 216
7 com.davie.klondike 0x000022a1 start + 41
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x927db6ae ecx: 0x90ac0010 edx: 0x00000041
edi: 0x00000008 esi: 0xbffffaf8 ebp: 0xbffffb88 esp: 0xbffffac4
ss: 0x0000001f efl: 0x00010202 eip: 0x90a594c7 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
What I've done to try and get it to run on tiger:
Set the following build settings in my target:
ARCHS = $(ARCHS_STANDARD_32_BIT)
SDKROOT = macosx10.4
MACOSX_DEPLOYMENT_TARGET = 10.4
GCC_ENABLE_OBJC_GC = unsupported
In the xib file, set the target to 10.4 (I've also tried saving a
version 2.0 nib instead of a xib).
I'm building using Xcode 3.1.2.
If anyone could point me to what setting I've missed, or some
documentation I can read on this, I'd be really grateful.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden