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

List:       kde-commits
Subject:    Re: Anyone want to look at a libtool problem? ;-)
From:       Stephan Kulow <coolo () kde ! org>
Date:       1999-11-01 12:50:33
[Download RAW message or body]

weis wrote:
> 
> Hi,
> 
> On Sun, 31 Oct 1999, Stephan Kulow wrote:
> 
> > Mosfet wrote:
> > >
> > > Hi. As the earlier logs show I ported kdvi to KParts/Konq. In doing this
> > > I needed to make most of it a shared library (libkdvi) and I hacked the
> > > Makefile.am to link to the kpathsea static library in the kdvi
> > > directory.
> > >
> > > Regretfully, my hack didn't work - it's linking to the system kpathsea
> > > library and everything I try makes libtool error with "Cannot link to
> > > non-libtool objects". KPathsea doesn't use libtool tho and is built
> > > static so I am hurting with this. Can anyone look at it?
> > >
> > > BTW: The shared library libkdvi *must* be the one linked to kpathsea,
> > > *not* the kdvi executable.
> > >
> > It's simple as: there is no way to link a module against a static
> > library. When I spoke with Torben about this flaw in canossa, he
> > said something like "Tja" :)
> >
> > The fix is simple: rewrite kpathsea's Makefile to use noinst_LTLIBRARIES
> 
> Then I will make killus libs shared, too.
> 
> I still had the hope that coolo found some magic solution in the meantime
> :-)
> 
That is the magic solution! :)

The trick is that noinst_LTLIBRARIES aren't shared libraries - they
are convenient libraries - meaning catted object files. These are
linked against the shared lib as it - without a reference to another
library. For convenience ... :)

Greetings, Stephan

-- 
As long as Linux remains a religion of freeware fanatics,
Microsoft have nothing to worry about.  
                       By Michael Surkan, PC Week Online

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