Re: Xcode 2.5 can't #include_next <stdarg.h>
Re: Xcode 2.5 can't #include_next <stdarg.h>
- Subject: Re: Xcode 2.5 can't #include_next <stdarg.h>
- From: Scott Tooker <email@hidden>
- Date: Mon, 5 Nov 2007 13:04:49 -0800
On Nov 5, 2007, at 10:44 AM, Steve Mills wrote:
On Nov 5, 2007, at 12:05:53, Scott Tooker wrote:
What Chris is saying is that you should reference individual
libraries
as if they come from the base system, but then set SDKROOT to point
to
the correct SDK to use.
That's what I was doing before - dragging .dylib's from /usr/lib
instead of from the sdk. When I did that, our app would not load on
a 10.5 seed because it couldn't find one of the libs. I was told to
use -bind_at_load to fix it, and to drag the .dylibs from the sdk
instead.
So which is correct?
First off, which libraries are showing this problem? I wonder if you
are attempting to link against a specific version of a dylib instead
of using the more generic symlinked version.
Scott
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden