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

List:       kde-devel
Subject:    PIC static libs, was: Re: kdenonbeta/khexedit2
From:       Josef Weidendorfer <Josef.Weidendorfer () gmx ! de>
Date:       2003-09-15 19:59:14
[Download RAW message or body]

On Monday 15 September 2003 20:51, Stephan Kulow wrote:
> Am Monday 15 September 2003 20:45 schrieb Josef Weidendorfer:
> > Opinions?
>
> In general I think it makes sense. Just: good luck trying to convince
> libtool to generate PIC code in an installed static library. A simple
> static library isn't good enough for KDE, then you can't use the widget in
> plugins.

Ugh, that's a technical problem I never thought of. You're right, widgets
not usable in plugins are not good.

But wait, how is kdeaddons/konq-plugin/fsview working at all?
There, I produce both a plugin and a application. To make this work with
automake, I have to use a static library with the widget, and this is linked
with both targets. What's the difference here?

Or is this a problem in kdeaddons/konq-plugin/fsview, leading to many 
relocations at load time because of the non-PIC TreeMap widget?

I have no idea how to make this work in another way. I can't put the same 
sources into 2 automake targets, or? Or I better trash the standalone 
version?

Josef

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