• 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: XCConfig file stoped working
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCConfig file stoped working


  • Subject: Re: XCConfig file stoped working
  • From: Jim Wintermyre <email@hidden>
  • Date: Fri, 26 May 2006 20:33:37 -0700

At 10:55 AM -0700 5/26/06, Scott Tooker wrote:
On May 25, 2006, at 6:24 PM, Jim Wintermyre wrote:

Hi Scott -

I'm a little confused about this response. I was doing something similar where I have /Developer/SDKs/MacOSX10.3.9.sdk/Developer/Headers/FlatCarbon as a header search path in my PPC target, and similarly one based off the MacOSX10.4u.sdk for the MacIntel target. I'm actually using the 10.3.9 or 10.4u SDKs as my SDKROOT in the corresponding targets as well. Are you saying that if I just have a header search path of /Developer/Headers/FlatCarbon for BOTH targets, that it will actually get based off of the SDKROOT, effectively doing the same thing I'm doing manually with the separate entries now? How does XCode determine when it needs to do this? (I have other entries in the header search paths that are not to system files.)

Including the users list since I'm sure others have the same question

Yes, we look at all the header search paths (in HEADER_SEARCH_PATHS and USER_HEADER_SEARCH_PATHS) and framework search paths (FRAMEWORK_SEARCH_PATHS) and see if $(SDKROOT)/<search path> exists. If it does, we use the SDK-based path, otherwise (AFAIK) we should use the original search path.

In your case, you just need to add /Developer/Headers/FlatCarbon to HEADER_SEARCH_PATHS, we should take care of the rest.

Ah, this is good to know. Thanks for the clarification.

BTW, if you have header search paths that are for your project files, I strongly suggest you add those to "User Header Search Paths" and then turn off "Always Search User Paths". This will ensure that we only look in the header search paths when looking for <>-style includes and use the user header search paths for ""-style includes.

Oh, I missed the "User Header Search Paths" option. I'll try that out.

Thanks,
Jim

_______________________________________________
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: XCConfig file stoped working (From: Scott Tooker <email@hidden>)

  • Prev by Date: Re: Try-catch broken in gcc4.0? (Solved)
  • Next by Date: CFMessagePort weirdness, szone_error, double-free?
  • Previous by thread: Re: XCConfig file stoped working
  • Next by thread: gdb problem
  • Index(es):
    • Date
    • Thread