• 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: Tue, 6 Nov 2007 08:10:40 -0800


On Nov 6, 2007, at 8:01 AM, Steve Mills wrote:

On Nov 5, 2007, at 21:01:01, Scott Tooker wrote:

Hmm, I was just able to add the libz.dylib symlink to a project in
Xcode 3.0 without issues. Are you saying that when you use the Project-
Add to Project... menu item in Xcode 2.5 you are unable to select
symlinks in that open dialog? If so you might try adding one of the
actual dylibs and then editing the path via the file inspector to have
it point to the symlink instead.


No, not via the Add to Project menu item. The libs were already a part of the project, so I selected each lib one at a time, did Get Info, then clicked the Choose button. It was in this Nav dlog that the symlinks were disabled. I just tried it again in 3.0 and 2.5 and both are working correctly today. #$%&! I hate bugs that only show up sometimes.

So, have you figured out why I'm being told to add the symlinks (instead of the actual libs) and to add them from the SDK (instead of from the OS), but previously was told to do the opposite in both cases? I really want to know which is correct.

As I understand it, you want to add the symlink from the base OS and then set your SDKROOT appropriately. I can't think of a good reason to directly add content from the SDK, since SDKROOT will (effectively) get prepended to all paths.


As far as the symlink goes, the SDK should have it's symlink pointing to the right version, so you should be clear there.

The one problem that could crop up is that the version that the symlink points to in the SDK doesn't exist anymore in the base system, leading to a run-time link error.

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

  • Prev by Date: Re: Xcode 2.5 can't #include_next <stdarg.h>
  • Next by Date: Re: NSString bindings are one-way in Xcode 3.0
  • 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