Re: Backwards compatibility
Re: Backwards compatibility
- Subject: Re: Backwards compatibility
- From: Michael Rondinelli <email@hidden>
- Date: Fri, 15 Aug 2003 16:37:28 -0400
On Wednesday, August 13, 2003, at 06:30 AM, Jeff LaMarche wrote:
>
> I've got a Cocoa program compiled using GCC3 on 10.2 with the latest
>
> (non-beta) developer tools. I've got a few users on 10.1 reporting
>
> that it doesn't work for them. I'm almost 100% that I haven't used any
>
> 10.2-specific functionality, so I'm wondering how I can compile a
>
> version that will run on 10.1. I don't have a machine with 10.1 to use
>
> to test.
>
>
>
> Does anyone know what steps can I take to produce (on 10.2) a binary
>
> that will run on 10.1? Will switching to GCC 2.9 do it? I don't have
>
> any frameworks linked other than Foundation and Cocoa, and am not
>
> using any of the new features added in 10.2.
>
>
>
> Any thoughts are appreciated. TIA.
>
> Jeff
On Friday, August 15, 2003, at 4:08 PM, Dustin Voss
<email@hidden> wrote:
>
If you set a compiler flag (in your target settings) like so:
>
-DMAC_OS_X_VERSION_MAX_ALLOWED=MAC_OS_X_VERSION_10_1
>
and recompile, you'll find out for sure what 10.2 stuff you're using.
>
>
Also, check out Apple's technote on the subject:
>
<http://developer.apple.com/technotes/tn2002/tn2064.html>.
This won't catch all of the symbols that are not available on 10.1.
Specifically, there are a bunch of standard library (C library)
functions that aren't implemented on 10.1. Things like: "float"
variants of mathlib functions, such as cosf, absf, etc., several printf
variants including asprintf, and some others. The headers for these
libraries do not use the convenience macros described above.
You can find out what is causing the problem at run time by checking
the console window (from the Console application in the Utilities
folder). You will see log entries such as this:
dyld: /path/to/myApp.app/Contents/MacOS/myApp Undefined symbols:
MyApp undefined reference to _asprintf expected to be defined in
/usr/lib/libSystem.B.dylib
The best way to find out about all these things is keep a 10.1
installation around to test your builds against. Almost invariably
there are issues that need to be resolved.
Best Wishes,
Michael
--
Michael Rondinelli
Chief Technology Officer
EyeSee360, Inc.
email@hidden
_______________________________________________
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.