Re: How to resolve this error ...
Re: How to resolve this error ...
- Subject: Re: How to resolve this error ...
- From: Jeffrey Walton <email@hidden>
- Date: Wed, 09 Nov 2011 11:23:35 -0500
On Wed, Nov 9, 2011 at 11:05 AM, koko <email@hidden> wrote:
> The pch file is at $(SRCROOT) and is not included by any file.
> The build setting for the pch file is $(SRCROOT)/LibEmbApp_Prefix.pch
> The path in error is created by XCode as I believe a hash of the project and
> target being built.
> Since this is an internally generated path I am at odds with how to get a
> build.
Open a terminal, and `cd` into the project. Open the project file with
a text editor (.proj extension, if i recall), and you can fix it by
hand. Macros such as SRCROOT are the name of the property (IIRC).
I had similar path problems when I upgraded to a universal binary.
When using Xcode, I could only get Xcode to change some (but not all)
project attributes through the UI. Precompiled headers was one of
them, and the target executable name was another.
Jeff
> On Nov 9, 2011, at 5:13 AM, Andreas Grosam wrote:
>
> On Nov 8, 2011, at 11:56 PM, koko wrote:
>
> Can anyone shed some light on the following error ... why it occurs and how
> to resolve it?
> -koko
> <command line>:4:10: fatal error: '/Volumes/DBREPOS/WORKING FROM
> SHOP/_working/LibEmbApp/_XC42/LibEmbApp.build/Release/LibEmbApp_Prefix-hcuaqxkaqphgpnbflnatukdqufcd/LibEmbApp_Prefix.pch'
> file not found [2]
> #include "/Volumes/DBREPOS/WORKING FROM
> SHOP/_working/LibEmbApp/_XC42/LibEmbApp.build/Release/LibEmbApp_Prefix-hcuaqxkaqphgpnbflnatukdqufcd/LibEmbApp_Prefix.pch"
> ^
> 1 error generated.
>
> Do you actually have this include directive somewhere in your source?
>
> #include "/Volumes/DBREPOS/WORKING FROM
> SHOP/_working/LibEmbApp/_XC42/LibEmbApp.build/Release/LibEmbApp_Prefix-hcuaqxkaqphgpnbflnatukdqufcd/LibEmbApp_Prefix.pch"
>
> what is "<command line>" ?
> Looks like, the preprocessor is bailing out, because it can't resolve the
> path to the included file "LibEmbApp_Prefix.pch".
> The path looks strange anyway. Usually, you place .pch files as siblings to
> the Xcode project file or into a target subfolder. This "precompile prefix
> header" should not be included via #include directives in any of your
> sources, instead there are build settings related to prefix files that
> compile it in a precompile build phase. You likely need to fix your build
> settings here.
> Andreas
_______________________________________________
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