• 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: Rick Ballard <email@hidden>
  • Date: Tue, 6 Nov 2007 11:14:15 -0800

On Nov 6, 2007, at 11:02 AM, Steve Mills wrote:
On Nov 6, 2007, at 12:48:55, Steve Mills wrote:
On Nov 6, 2007, at 12:26:40, Scott Tooker wrote:
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.

OK, thanks. I guess I'll change them all back again.

So what should the Path Type be? Note that all Xcode 2.4's will be updated to 2.5, so the Relative to Xcode folder Path Type will be available. Should that be used to Xcode can locate the .dylib or .framework in the correct SDK folder? Or is Absolute Path good enough?

The Relative to Xcode folder path type should only be used for references to content inside the Xcode folder. Since the generally recommended practice has been for your project to contain a reference to the file in your system, it should be an absolute path. The SDK comes into play after a reference has been resolved to a file on disk, so the path type won't affect how the SDK is applied.


If you were to add a file directly from an SDK to your project, as DTS originally suggested, you would in that case want it to be a Relative to Xcode folder path type. As Scott said, that's not been our recommendation, and shouldn't be necessary, though I suspect that it should actually work – the fact that the file type of such references get set to "compiled.mach-o" instead of "compiled.mach-o.dylib" is likely just a bug that hasn't generally been a problem due to the fact that this isn't common practice.

	- Rick
_______________________________________________
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


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

  • Prev by Date: Re: [Xcode-Users] AppleScript Command for "Open Quickly"?
  • Next by Date: Re: Xcode 2.5 can't #include_next <stdarg.h>
  • 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