Brainstorming the debugger problem
gigafalk at yahoo.com
Mon Mar 20 07:34:08 UTC 2000
Ralf Funken wrote:
> I think we agree that the key problem is to find out where the executable is,
> so we can call the debugger with it. Maybe it's not so difficult to find out
> after all. As far as I can see there are only two posssibilities: either it's
> in the projekt dir or in .libs.
I use customer kdevelop-projects (with external Makefiles). Our
binary/shared objects are neither in the project dir or one of its
subdirs nor in .libs. In a tmake-generated Makefile it's possible to set
any destination dir. Ours is in a central place (depending on our
In MSVC6.0 it's possible to set the place of debug-target in the project
file (.dsp). I think KDevelop should handle it in the same way.
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
More information about the KDevelop-devel