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: Steve Mills <email@hidden>
- Date: Mon, 5 Nov 2007 12:44:01 -0600
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?
In the future it would be nice if Xcode had a
more abstract way to add frameworks that wasn't just browsing the file
system (since in the future you may not end up installing headers and
other developer pieces in the base system. For example, consider the
UI presented when choosing an AppleScript dictionary in Xcode in
Script Editor. In that case you just have a list of applications to
choose from. You could image a similar interface for choosing
libraries or frameworks.
I agree whole-heartedly. There would be no question as how this should
work if Xcode would just shows you what's available and let you choose
from a list, rather than making the user try to figure out if they
should come from the OS path or from the sdk. That's really not good
user friendliness.
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