• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Choosing not to run on 10.1
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Choosing not to run on 10.1


  • Subject: Re: Choosing not to run on 10.1
  • From: Yojimbo <email@hidden>
  • Date: Mon, 24 Feb 2003 20:56:16 -0800

Date: Mon, 24 Feb 2003 23:19:10 -0500
Subject: Choosing not to run on 10.1
From: Andrew Thompson <email@hidden>
To: cocoa dev <email@hidden>

I have a Cocoa application that requires Jaguar to run.

I've read technote 2064
(http://developer.apple.com/technotes/tn2002/tn2064.html), and I
understand about weak linking and have defined MACOSX_DEPLOYMENT_TARGET
and MAC_OS_X_VERSION_MIN_REQUIRED accordingly.

What I want to know is, what happens if a 10.1 user runs this
application?
Will the app just bounce a couple of times then quit? Or will there be
a nice dialog informing the user that the application requires 10.2 and
can't be run?

If this is not built in to the OS, does anyone have any suggestions
about a good way to provide such a dialog?

Should I do something like call Carbon in main.m before
NSApplicationMain() is called?

AndyT (lordpixel - the cat who walks through walls)
A little bigger on the inside

(see you later space cowboy ...)

Simple answer... it fails to launch (ie. bounces once mabey 3 times on a G3 and exits without any notification).

MAC_OS_X_VERSION_MIN_REQUIRED was included as of 10.2.3, if I remember correctly though it may have been 10.2.1, so it won't even help you fully identify 10.2 sub versions, but it's a heck of a lot better than nothing at this point.

The problem you're going to have is that you really won't be able to run the core application at first, unless you can avoid loading any resource but your check code, which frankly, would give me a headache. If you REALLY need this you might consider making the primary executable a wrapper, be it a script or another low profile executable, that checks the system version and launches the application directly if everything checks out.

There might be other suggestions out there, but that's the one people keep telling me about. You'll notice that the majority of Apple's iApps don't even try to solve this problem so you might be able to get away with a simple ReadMe :)

Hope that helps,
Jim
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Choosing not to run on 10.1
      • From: Dennis Munsie <email@hidden>
  • Prev by Date: Re: New to Cocoa
  • Next by Date: NSBrowser Problem
  • Previous by thread: Choosing not to run on 10.1
  • Next by thread: Re: Choosing not to run on 10.1
  • Index(es):
    • Date
    • Thread