Re: Problem Debugging GNU Make Projects
Re: Problem Debugging GNU Make Projects
- Subject: Re: Problem Debugging GNU Make Projects
- From: Jim Ingham <email@hidden>
- Date: Tue, 1 Feb 2005 11:16:12 -0800
Tony,
Please file a bug with your example project and where you tried to set
breakpoints, and what I should do with the project to try to hit thost
breakpoints, and I will have a look at it.
I have been using an Xcode project for debugging gdb on and off for a
couple of years now, and haven't had problems with finding sources in
the debugger. gdb is a very complicated project with LOTS of
subdirectories and code generated by the configure/make process, etc.
But all this works for me.
So there must be something particular to your project that is tripping
Xcode up.
Jim
On Feb 1, 2005, at 8:36 AM, Tony Cebzanov wrote:
Well, since I posted this last week, I've had two list members tell me
they're in the same boat. This, to me, says two things:
1. There's no solution, or if there is, it's not widely known.
and
2. Use of XCode for GNU Make projects isn't just a niche market, so
there is definitely demand for debugging them properly in XCode.
With that in mind, I submitted a bug report to Apple, but to be honest,
my hopes aren't high that it'll get addressed anytime soon. So, does
anyone else out there have a workaround where they've been able to
debug, step into, set breakpoints, etc. in multi-level GNU Make
projects?
Thanks.
-Tony
Tony Cebzanov wrote:
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?
_______________________________________________
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
_______________________________________________
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