• 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: search paths
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: search paths


  • Subject: Re: search paths
  • From: Andreas Grosam <email@hidden>
  • Date: Wed, 30 Mar 2005 20:27:14 +0200


On 24.03.2005, at 22:44, Steve Mills wrote:

What do I have to do to get Xcode to find <string>? command-shift-d finds it just fine, but #including it doesn't. If it makes any difference, I'm working in Xcode 2.0, so it probably can't be discussed in public. But if somebody from Apple could contact me directly, I'd really appreciate it. My Spotlight project was able to build in previous Tiger builds.

Unless you compile with option -nostdinc++, the compiler (or better preprocessor) searches in standard system headers which are set implicitly. Standard system search paths are hard wired into the compiler and cannot be changed (but disabled via -nostdinc).


Thus, you do not need to set header search paths explicitly for standard headers.

The command-shift-d thingy just searches in customizable predefined search paths, which do not necessarily match any search paths relevant for your build. These paths are orthogonal to the search paths set in the build settings.
So a header which opens nicely in an editor via command-shift-d , might not be the header you expect and which will be actually inlcuded by the compiler.
IMO, this is at least confusing.


What you did experience (probably), is that the indexer will not parse C++ headers. That means, C++ headers will not appear in the headers-popup, nor will the symbols listed from them. The indexer will also refuse to parse headers having uncommon file extensions.
IMHO, this is one of the various missing features. Furthermore, the indexer gets pretty confused or just lacks to produce detailed information when parsing C++ source code, like namespace or qualifiers as well as templates, local classes.


Regards
Andreas



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:
email@hidden


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
  • Follow-Ups:
    • Re: search paths
      • From: Steve Mills <email@hidden>
References: 
 >search paths (From: Steve Mills <email@hidden>)

  • Prev by Date: My project uses source files with same name
  • Next by Date: Set chosen from list question
  • Previous by thread: search paths
  • Next by thread: Re: search paths
  • Index(es):
    • Date
    • Thread