Re: #include files <> vs "" not found?
Re: #include files <> vs "" not found?
- Subject: Re: #include files <> vs "" not found?
- From: "David M. Cotter" <email@hidden>
- Date: Wed, 2 Jul 2008 13:47:05 -0700
it was a project i had inherited, so i hadn't built it from scratch.
it had been converted previously from a CodeWarrior project and had
never compiled.
the problem was the "project" settings vs. the "target" settings. i
was doing all my settings in the project, and had not considered the
target settings (since this is the way i typically work)
finally i figured that out, i went and deleted all the target
settings, and re-implemented them in project settings (with
configurations)
now all is well
On Jul 2, 2008, at 1:31 PM, Chris Espinosa wrote:
On Jul 1, 2008, at 12:31 PM, David M. Cotter wrote:
in "prefix header" is the path to my PCH file and i have
"precompile prefix header" is checked
in "header search paths" it points to say an external source tree
(but it's my code, not the system's code or framework), consisting
of "system" headers (so i'd want to use <> to #include them)
tho i would not think i'd need this because all those headers are
also ref'd in the project.
and "user header search paths" it's empty, cuz all the files are
just included in the project. but i tried putting the same there
too.
anyway go to compile PCH and it barfs on the first #include that
has <> around it.
why?? is "header search paths" something OTHER THAN "system"
search paths? i thought this pref was related to using angle
brackets?
Perhaps the actual input to and output from the compiler might be
easier to read than your description. Please copy and paste it from
the build transcript so we can see what's going on.
If it's not in /usr/ or /System/Library, it's not a system header,
and should be in double quotes.
If it's in an external source tree, make sure that a name for that
source tree is set up in Xcode > Preferences > Source Trees, then
put the name of that source tree inot the User Header Search Paths.
But this is all a shot in the dark without any real information to
go on; just one "CompileC" line from the build transcript, along
with its output, ans nome notion of what header you're looking for
and where it actually resides, would be enough to solve your problem.
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