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

List:       kde-devel
Subject:    (a bit OT) linking additional libs with KDevelop
From:       mh <moloch () nikocity ! de>
Date:       2000-10-08 16:31:42
[Download RAW message or body]

Hi,
sorry if this is somehow OT,
but I searched the kdevelop list archive and asked this question on the kdevelop
list without success :-(
I'm using KDevelop1.2 (SuSE 7.0 and KDE1.1.2) to develop a
"pure" Qt2.2.x application, that was generated with the
app wizard based on the "Qt2.1 MDI" template. I've replaced the generated
files (main.cpp etc.) with my own implementations.
When I now try to link an additional library, I get a (IMHO) strange error.
Let's say, I add -lbla to "additional libraries" in the linker tab of the
dialog that appears when I choose the "Project->Options" menu.
I have a symlink libbla.so under /usr/local/lib which points to
/usr/local/lib/bla/libbla.so.1.0.3.
When I now try to run my app, I get the following error at linking stage:

g++: /usr/local/lib/.libs/libbla.so: No such file or directory

When I add the absolute path to the "Project->Options" dialog like
/usr/local/lib/libbla.so, everything works fine.

If I generate a Makefile with tmake and add a line 
LIBS = -lbla 
to the .pro file, everything works too. Therefore I don't think there's a
problem with my installation.

It's also possible to compile a small test app from the command line like
g++ test.cpp -lbla -o test
without problems.
Does someone have an explanation why the library is searched under
/usr/local/lib/.libs (especially why .libs is appended to the path)? 
Or am I doing something wrong? 

Thanks a lot,
Michael

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

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