oops i forgot i had overridden the debug variable to -ggdb, but still no difference…
is there any difference between -ggdb and -g3?
is there any way to build a glx program without threads?
this is really my last step to a decent linux development environment. i’ve managed to set up anjuta for a decent ide, though i’m not using it for building… i have to manually use symbolic links to the top level directory in its ‘project module sub-directories’, but other than those minor inconveniences it beats msvc hands down. well so far at least, once i start bringing my work in, i’m sure the complete builds will be relatively intolerable… i will have to figure out the autotools, because i don’t think anjuta is up to the task in the build department, at least not for my purposes.
it would be nice though if konqueror allowed for linking files with the drop down box similar to the mouse/menu ‘copy/paste’ procedure.
make is not procedural, but i don’t know that library tags are kept, so maybe the order might make a difference??? still i might think that it wouldn’t compile if so… i’m just trying to cover all of the bases.
Hmm, I’d say it couldn’t hurt if you have a look at the make manual: gnu make You don’t need to read the whole manual.
Just get an overview about make.
And here is the link to the compiler documentation you’re probably using: gcc
naturally i’ve been regularly consulting the make and gcc man and info resources.
my question though, is i assume you’ve read the said material to an extent so much to satisfy your curiosities. so unless you are holding back some useful suggestions, i can’t imagine how my cover to cover assimilation of those materials would shed any light on my gdb dilemma.
naturally i first consult any and all available resources even vaguely related to the problem at hand.
follow up: i did find a simple mouse method to make links of large groups of files. it is only that the source and destination ‘directories’ must be open. -michael
Originally posted by <michael>:
[b]naturally i’ve been regularly consulting the make and gcc man and info resources.
my question though, is i assume you’ve read the said material to an extent so much to satisfy your curiosities. so unless you are holding back some useful suggestions, i can’t imagine how my cover to cover assimilation of those materials would shed any light on my gdb dilemma.
naturally i first consult any and all available resources even vaguely related to the problem at hand.
sincerely,
michael[/b]
I didn’t want to offend you but I had the impression that these manuals could be useful to you.
The only ‘useful’ information I could find was the suggestion to upgrade gdb to the newest version.
There are ways to code an OpenGL app without using glx directly. For example, I use SDL for windowing and input. This enables me to use the same source for Windows and Linux.
I use GDB extensively without any problems.
Another tip - never, ever try to debug a full-screen app that grabs the mouse. I can’t tell you how many times I have done that. The app freezes on the breakpoint, but there is no way to get back to GDB without the mouse. At that point, I usually ctrl-alt-f7 to a console prompt, manually kill the process, then return with f7. Then try again with the app properly windowed and mouse left ungrabbed.
to your XF86Config file in the ServerFlags section, you can use Ctrl+Alt+Keypad-Divide to deactivate the mouse/keyboard grab without killing the app. I usually start my fullscreen app on one workspace and use a hotkey to switch to a different workspace that has my debugger window.
This has security implications if you’re using a locking screensaver though.
Don’t have any advice on the gdb problem, but as for automatic build environment I think http://www.scons.org/ is a fairly good choice. Uses Python as its scripting language. It is far simpler to use than the autotools in my opinion, so you might want to give it a try.