• 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: VERY Newbie question: include paths
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: VERY Newbie question: include paths


  • Subject: Re: VERY Newbie question: include paths
  • From: Markian Hlynka <email@hidden>
  • Date: Tue, 2 Nov 2004 16:35:39 -0700

Thank you both.

To paraphrase a douglas-adamsian door, "Pleased to be of service".


This confirms the conclusions I was reaching. I am somewhat familiar with gcc but never used it on a large project (one reason I'm switching). I looked at the gcc input in the build window and realized that is impractical to think that you could have an -I setting for every embedded header file. I have been considering moving to a more unix styled source tree anyway.

That said though... Is there any case in Xcode where a header file reference in the source group or target will affect the -I paths passed to gcc? I have seen no evidence of this, but the documentation and other posts in this list imply it.

I'm not sure of this one. I did want to point out, incidentally, that the flaw, insofar as it is a flaw, is not truly with xcode. This is how gcc is designed, and the xcode designers tried really hard to give us a graphical representation of this. Because gcc was never designed with graphical representation in mind, it's certainly not the xcode team's fault that it's a little less than obvious. The striking-out of overridden settings, while not immediately intuative, is actually akin to a stroke of genius once you realize what it means.


So, to the xcode team, I want to say that you've done well. Where we gripe and say there's room for improvement, well, we're not saying we don't believe you tried your damndest! You've done GREAT, just please don't stop improving Xcode!


My only gripe is that this is so basic, I would expect the "Getting Started..." doc to say something specific about the include path setting.

I do agree that this is non-obvious, and one part of xcode that could be refined is access to certain types of documentation, especially with the novice in mind. Though, of course, I understand that this isn't really an xcode thing... it's a gcc thing wrapped up in an xcode thing, making one think it should be like a metrowerks or MSVisualStudio thing, when it isn't!


Markian

_______________________________________________
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: 
 >VERY Newbie question: include paths (From: Andy Wiese <email@hidden>)
 >Re: VERY Newbie question: include paths (From: Brian Smith <email@hidden>)
 >Re: VERY Newbie question: include paths (From: Markian Hlynka <email@hidden>)
 >Re: VERY Newbie question: include paths (From: Andy Wiese <email@hidden>)

  • Prev by Date: Re: VERY Newbie question: include paths
  • Next by Date: RE: VERY Newbie question: include paths
  • Previous by thread: Re: VERY Newbie question: include paths
  • Next by thread: Re: VERY Newbie question: include paths
  • Index(es):
    • Date
    • Thread