Re: Build warning when SDK = 10.1.5
Re: Build warning when SDK = 10.1.5
- Subject: Re: Build warning when SDK = 10.1.5
- From: Kevin Grant <email@hidden>
- Date: Fri, 23 Jan 2004 22:29:24 -0600
The 10.1.5 SDK should really only be used with gcc2.95.2, as there are
certain aspects of the Cheetah standard libraries that are
incompatible with gcc3-series compilers. Code you build with
2.95.2/10.1.5 will of course run on later OS releases, but cannot take
advantage of new features in those releases, because to do so would
require the weak-linking functionality that was introduced in 10.2.
(One of those changes was the addition of libraries to /usr/lib/gcc
for gcc 3.1 and later, which is why they're not there on 10.1.5 and
why gcc 3.3 is looking for files there).
So the 10.1.5 SDK is most useful for building products pretty much
exclusively for 10.1.
It is possible to manually load frameworks and use symbols from later
OSes (conditionally, of course) within code built against the 10.1.5
SDK and GCC 2.95.2. But I'd be lying to you if I said it wasn't a real
pain when you wanna use an API. :) On later OSes you basically
manually locate and load frameworks, and suck API pointers into
variables if they are available, such that pointers to newer APIs are
only callable through your variables. Yep, painful. :)
This alternative is actually described in an Apple technote on the
subject of weak linking, but I have some nifty code which makes the
whole thing relatively painless. If your links are getting you in a
bind, just ask. :)
Kevin G.
http://homepage.mac.com/kmg/
mail to kevin at ieee dot org
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.