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

List:       kde-devel
Subject:    Re: link problems (was kspell angst)
From:       Duncan Hughes <dunch () dunch ! demon ! co ! uk>
Date:       2002-06-25 13:23:13
[Download RAW message or body]

>On Tuesday 25 June 2002 13:51, Duncan Hughes wrote:
>> >I don't see kspell here. Do you link to it?
>> >(add -lkspell or $(LIB_KSPELL) to the LIBADD line, in Makefile.am).
>> >If you do so already... check for a libkspell.a (static lib) lying 
>around, 
>> >that would create problems.
>> >
>> 
>> I've tried linking to kspell every way I can think of.
>> I've checked the KSpell box under "linker options" in KDevelop, I've added 
>> -L/opt/kde2/lib (additional flags) -lkspell (additional libraries) to 
>"linker 
>> options" 
>
>Did that add -lkspell to the Makefile.am ?

nope, KDevelop seems to be ignoring an libraries I've told it to add.  kspell 
isn't mentioned at all in Makefile.am (unless I've added it manually).
However, I've had some partial success by cut 'n' pasting the last g++ line 
from KDevelop's compile window, adding -lkspell and running it by hand.  This 
has got my code running and has got my boss off my back :-)
OK, I'm satisfied that there is no problem with my system, just with KDevelop.


>> in KDevelop and now I've added a line LIBADD = $(LIB_KSPELL) to 
>> Makefile.am (taking care to avoid the "KDevelop will modify this part" 
>> section).
>
>No, what you want is libddiview_la_LIBADD = ... $(LIB_KSPELL)
>(in the kdevelop-generated section, where ... is the existing stuff there.
>Just don't regenerate your Makefile with kdevelop after that).
>
>> Like I say, I've tried everything I can think of and I'm still completely 
>> stumped.  I'm pretty sure it's a pretty basic configuration problem, as 
>the 
>> library is there and it contains the symbol I'm looking for.  It's just 
>not 
>> getting linked in and I have no idea as to why.
>
>As long as you don't manage to get the link line to contain -lkspell, it 
>won't work.
>
>> Is it possible to run a static lib as a Kicker applet or through 
>appletproxy?
>
>Nope. 


KDevelop seems a lot happier linking static libs, I've managed to work around 
similar problems with other libraries in the past by linking statically.
Many thanx for your help David, I can see that I'm going to have to look into 
KDevelop and the automake process more closely and see if I can find a way to 
force including a shared library when linking.  If you (or anyone else for 
that matter) know a quick way of doing this please let me know, but I think 
I'm going to move my question to the KDevelop list as the question would seem 
more relevant there.
Thanx again.
dunch.


 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]