• 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: wrong file #included
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wrong file #included


  • Subject: Re: wrong file #included
  • From: Chris Espinosa <email@hidden>
  • Date: Fri, 12 May 2006 13:01:55 -0700


On May 12, 2006, at 11:28 AM, James W. Walker wrote:

I have 2 versions of a file that I'll call foo.h, obviously in different directories.  One of the files belongs to my project.  The other one is not in the project and is not within any header search path.  Yet, when compiling a source file that says #include "foo.h", Xcode insists on picking the wrong one, causing a compile error. What is it that I'm failing to understand about how Xcode finds files to include?


Of course I could rename one of the files, but since both are in CVS, it's a pain.  And I'm worried that this problem may occur again in a less obvious way.


Please add -v to your Other C Flags and Compile the file that is causing the error, and send it to me (offlist if you're not comfortable posting it here).  It would help to know the full paths to the two different foo.h files as well.  

Chris
 _______________________________________________
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: 
 >wrong file #included (From: "James W. Walker" <email@hidden>)

  • Prev by Date: Re: wrong file #included
  • Next by Date: Re: Compiler bug?
  • Previous by thread: Re: wrong file #included
  • Next by thread: Forcing CodeSense to index a framework
  • Index(es):
    • Date
    • Thread