Rob Bradford wrote:
On Mon, 2008-03-17 at 19:16 +0800, Max Waterman wrote:
Rob Bradford wrote:
On Mon, 2008-03-17 at 10:31 +0800, Max Waterman wrote:
"Automatically?". I had assumed I have to specifically link with the
debug libs; but when I try, I get OpenGL link errors.
"OpenGL link errors" ?
The debug packages work by putting the stripped out debug information
into /usr/lib/debug and modifying the ELF headers of the stripped
library to tell it where to look. GDB then uses this to find the debug
information and load it in.
Hrm - I'm not sure I understand these issues so well. This is all
different to IRIX :| We just linked with debug version of the libraries
instead of the regular ones and pointed the debugger at the root of the
source code so it knew what code to display.
Similarly if you build from trunk
you'll find that it gets built with line number information included.
If you want something graphical, don't use Eclipse it doesn't work very
well. I'd recommend Nemiver or Anjuta.
Well, I don't much care for graphical things, but it does seem to be
popular and thought it was worth learning while I had something to use
it for. I can't say I've been impressed, but I've been trying to reserve
judgement until I've tried harder :|
I was able to checkout and compile your 'clutterfly' demo and it sort of
worked for me ;-)
Excellent :)
Yes, there are still problems. Like, why does it only sense my 'events'
in the bottom right quadrant of the button. Is this something to do with
the me changing the size of the button and moving it's anchor? I had
trouble with that before - the anchor moved but set_size() still adjusts
from the top left of the rectangle, not either side of the rectangle.
However I noticed a bug in your Makefile that means you won't get
debugging information for you own code:
Your .c: target should look like this:
.c:
$(CC) -g -Wall $(INCS) [EMAIL PROTECTED] $(LIBS) -o $@
(Notice the addition of -g.)
Yes, I put that in deliberately. Is that an error? That's to stop the
compiler stripping out info I need for debug, no? I've even done Linux
development (Montevista linux on Motorola phones) so I should already
know this sort of thing - amazing what you can forget in a couple of
years :|
I think I still need help doing this. I'm sure there must be some good
guides on the 'net, and I have looked, but to no avail (hence this
thread, really). I loved the tutorial and wished I'd found it last week
when I started this - no mention of it on the web site that I could see,
and I didn't spot it in the source tree :|
Any ideas where there might be a good guide on using debug libraries and
source trees? ...or should I just bite the bullet and compile from svn?
And wrt. to your comment about #clutter, you're probably going to have
most luck 10-6 Monday to Friday UK time.
I figured as much :)
Max.
Regards,
Rob
--
To unsubscribe send a mail to [EMAIL PROTECTED]
