[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: How can I debug part of kdebase?
From:       Kuba Ober <winnie () hoth ! amu ! edu ! pl>
Date:       2001-01-11 13:55:50
[Download RAW message or body]

On Wednesday 10 January 2001 03:40 pm, Kuba Ober wrote:
> On Wednesday 10 January 2001 03:27 pm, Brian Wagener wrote:
> > I am trying to modify kwrite, but I am having some problem.  Well my
> > changes are crashing the program so I would like to run it through gdb
> > to find the problem, though the file kwrite is a shell script to run
> > ..libs/kwrite, but if I run .libs/kwrite, it runs the kwrite that is
> > installed in the system, and not the modified version.  What is up
> > here?  What am I missing?
>
> Well, just run your program with explicit path, like
> ... /home/panic/kwrite/src/kwrite
> Or am I missing something?

Uh-oh commenting on myself ;-). Now I get it I think;-). Kwrite's 
functionality - especially the kwritepart - must be in a library somewhere.

So when you call kwrite, it uses whatever installed library there is and 
ignores your local (newly compiled) stuff. According to libtool docs 
info:/libtool/Linking executables
there's a wrapper script which makes sure that right libraries get called.

Well, in that case, if you build your executable and its libraries, make sure 
that you put a different prefix for configure, like configure --prefix=~/test
rather than default /usr or whatever. This should make your executable use 
all local libraries.

Kuba
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]