Problem Debugging GNU Make Projects
Problem Debugging GNU Make Projects
- Subject: Problem Debugging GNU Make Projects
- From: Tony Cebzanov <email@hidden>
- Date: Thu, 27 Jan 2005 18:54:52 -0500
I am trying to use Xcode as an editor/debugger for a project which needs
to run on a lot of platforms. This means use of automake, autoconf, and
libtool for the builds, and use of the GNU Make project type, with an
external build target.
Setting the project up, editing files, etc. was easy, but when I got
compile warnings/errors, double-clicking on them was not bringing up the
offending source files, even though they had been added to the project.
After some hard thinking, it occurred to me that Xcode might not be
looking for them in the right subdirectory of the project, which has
different subdirectories for different parts of the library.
Sure enough, when I created a "flat" project with only one directory,
Xcode was able to bring up source files when there were compile
warnings/errors.
So, I'm left wondering if there's any way to find debugging happiness in
this environment. Creating separate, flat Xcode projects with a single
directory each isn't feasible, because there are so many directories,
and managing dependencies between projects would be a nightmare. What
I'm hoping is that there's some setting, feature, or trick to getting
Xcode to be able to know what subdirectory it's in, so that when an
external target is building in a subdirectory, it can bring up the
relevant source file.
Whew. That's certainly a mouthful, I hope I asked my question clearly.
So, is it doable?
Thanks.
-Tony
_______________________________________________
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