• 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: Xcode 2.5 can't #include_next <stdarg.h>
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 09:08:09 -0800


On Nov 5, 2007, at 7:45 AM, Steve Mills wrote:

On Nov 3, 2007, at 21:09:44, Chris Hanson wrote:

On Nov 2, 2007, at 10:39 AM, Steve Mills wrote:

It was when opening the 2.4 project in 2.5, then changing the libs to come from /Xcode2.5/SDKs/MacOSX10.4u.sdk/usr/lib/ instead of / usr/lib/.

Don't do this; the libraries should continue to come from /usr/lib, not from the SDK directory.


Essentially, the rule is: Add items to Xcode from the root filesystem, let Xcode pull them from your specified SDK for you.

It works this way because essentially all of the tools that Xcode uses implement a mechanism like -isysroot, which tells the tool (like the compiler or the linker) to use a different directory than / for its root. Thus when you specify $(DEVELOPER_SDK_DIR)/ MacOSX10.5.sdk as your SDK, you're really saying to the tool set "use this directory instead of / when looking for headers and libraries."


Now I'm confused. I used a support incident to figure out why our app would not load in some of the 10.5 seeds. During that exchange I was told to use the sdk libs, NOT the OS libs.

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. 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.


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
References: 
 >Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Chris Espinosa <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Rick Ballard <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Rick Ballard <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Chris Hanson <email@hidden>)
 >Re: Xcode 2.5 can't #include_next <stdarg.h> (From: Steve Mills <email@hidden>)

  • Prev by Date: Weird scrolling in Xcode 3
  • Next by Date: NSTextView value binding gone in new IB?
  • Previous by thread: Re: Xcode 2.5 can't #include_next <stdarg.h>
  • Next by thread: Re: Xcode 2.5 can't #include_next <stdarg.h>
  • Index(es):
    • Date
    • Thread