Re: Target ignoring search headers
Re: Target ignoring search headers
- Subject: Re: Target ignoring search headers
- From: T Anthony Allen <email@hidden>
- Date: Fri, 10 Mar 2006 17:44:53 -0500
You gotta love xcode. I just recreated the target (again, about the
fourth time) and it now works like a champ. My threat with the 2x4
must have worked but who knows why? I was planning to PROVE to you
all that it was acting all balky and then success. Its perverse :-)
By the way, I am a heavy eclipse user in addition to using xcode.
Eclipse has a feature that I use all the time, it can show you a list
of all references to a field or method. Does xcode provide such a
feature?
Tony
On Mar 9, 2006, at 7:24 PM, Chris Espinosa wrote:
On Mar 9, 2006, at 2:17 PM, T Anthony Allen wrote:
Using xcode 2.2, I have a C++ project in which I created a command
tool target. I edited the target to specify a header search path
in the search headers option of the build tab. When I build the
target, the header search path is being ignored and is not added
to the compile directives so the build fails because the compiler
cannot resolve the includes that would be found in the header
search path that I added. A similar target that I created long
ago, probably in an earlier version of xcode, does not have this
problem.
What size 2x4 should I use and where should I apply it to make
xcode include the header search path in the build? Right now the
2x4 is being applied to my forehead out of frustration.
You know that 2x4s aren't actually 2 by 4 inches, don't you? :-)
Be sure that:
a) You are editing the correct configuration of the target (for
best results with search paths, you should probably be editing "All
configurations")
b) If you're using any build settings (like $(SRCROOT) ) expanded
in your paths, that the whole is quoted to guard against spaces, etc.
It would help, as always, if you would copy and paste the portion
of the build transcript that's relevant to the problem (in this
case, the compiler invocation and errors) so we can see whether
indeed the paths are or are not being passed. You can do this by
simply selecting the "Compiling foo.c" and following "Error:
include file not found" lines from the build log and dragging and
dropping them into a Mail message.
Similarly, seeing the actual build settings for your target would
be a big help. Open the Target Settings, select the configuration
in question, pick the "Customized settings" group, select all, and
just drag and drop them into the reply.
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