Re: VERY Newbie question: include paths
Re: VERY Newbie question: include paths
- Subject: Re: VERY Newbie question: include paths
- From: LHM World Limited <email@hidden>
- Date: Tue, 02 Nov 2004 15:11:02 +0800
I come across exactly the same problem.
I am trying to compile a PC project on the Mac using XCode, and it broke all the import statements.
All header files must be added to the Target (adding to Project alone is not enough), AND be placed immediately at the Headers directory. This breaks everything.
Tried to get help, but still stuck at this point... guess i have to go back to the PC.
On Tuesday, November 02, 2004, at 02:40PM, Andy Wiese <email@hidden> wrote:
>My apologies for this most basic of questions. I really have tried to
>RTFM, I promise!
>
>I am trying to build a new Xcode project to replace a fairly large
>CodeWarrior project. The CodeWarrior import facility puked, but I
>prefer to build a new project from scratch anyway. Only I'm not having
>much luck so far.
>
>Xcode isn't finding my header files (all basic .h files). I have a
>large source tree which I have added to the project, but not added to
>the target. I have a basic main.c file which I added to the target. I
>have one main header file M_.h which includes all of the public .h
>files in the project.
>
> From what I can tell from the minimal documentation and reading this
>list, I expect a header file to be found if I have added it to the
>project, regardless of adding it to the target. Have I misunderstood?
>
>If I add #include "M_.h" to the prefix file, for precompiling, it is
>not found. If I add it to the main.c file it is not found. I added a
>Headers phase to the target, and added the header file to the Headers
>phase; it still is not found. If I move M_.h to the project directory,
>it is found. Or, if I add an explicit Header Search Path in the target
>build settings, it is found. However, during compilation of the M_.h
>header, none of the headers it includes are found. It is not reasonable
>to add a search path for each included file, so if I must rely on the
>explicit path method, I will have to reorganize the file structure of
>the project.
>
>Is there a way for Xcode to find my header files during compilation
>without specifying all the search paths in the build settings?
>
>Thanks for any hints,
>
>Andy
>
> _______________________________________________
>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
>
>
Best regards,
Charles So
LHM World Limited
http://www.lhmworld.com
+852-9263-1965
_______________________________________________
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