• 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: Thu, 1 Nov 2007 14:07:22 -0700

On Nov 1, 2007, at 10:08 AM, Steve Mills wrote:

On Nov 1, 2007, at 11:53:52, Rick Ballard wrote:

Make your SDK paths begin with "$(DEVELOPER_SDK_DIR)" instead of / Developer/SDKs. This isn't necessary when setting SDKROOT – Xcode will translate /Developer/SDKs to $(DEVELOPER_SDK_DIR) automatically for you in SDKROOT, but doesn't do this for SDKROOT_i386, SDKROOT_ppc, or a SDKROOT set in an .xcconfig file.

Ah, cool. Thanks! That fixed its wagon.

Using $(DEVELOPER_SDK_DIR) in your project will make it incompatible with Xcode 2.4.1, which doesn't know about that value, so you'll need to switch to 2.5 on 10.4.10 to work with a project that you've done this to on Tiger.

I think you meant to say Leopard here, yes? This is why I always use the numbers instead of the code names. :)

Sorry, let me rephrase: If you change your project's SDKROOT_i386/ppc settings to be relative to $(DEVELOPER_SDK_DIR), and if you want to use that project on Tiger-based tools after doing so, you'll need to use 2.5 instead of 2.4.1. On Leopard the only supported tools – 2.5 and 3.0 – both work fine with $(DEVELOPER_SDK_DIR).


When Xcode 2.5 (or Xcode 3.0 using the "Xcode 2.4-compatible" project format) automatically translates /Developer/SDKs to $ (DEVELOPER_SDK_DIR) for you in SDKROOT, it leaves a value of / Developer/SDKs recorded in the project file to preserve 2.4 compatibility.

This part confused me a bit. You say it "leaves a value of / Developer/SDKs recorded in the project file to preserver 2.4 compatibility." Does this mean compatibility that's used internally when running Xcode 2.5, or does it mean that I really don't need to upgrade all 2.4.1's to 2.5 on our 10.4.1 machines?

I mean that people just using SDKROOT don't need to upgrade all 2.4.1's to 2.5 on their 10.4 machines... but since we don't do that translation for SDKROOT_i386/ppc, you will need to.


If upgrading your 10.4 machines to 2.5 isn't possible for some reason, there may be another way to work around the issue, but upgrading to 2.5 is a lot simpler.

	- 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


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

  • Prev by Date: Re: Xcode 3 unresponsive after Save or opening Project Settings?
  • Next by Date: Re: #if for current SDK...?
  • 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