[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: Mosfet <mosfet () jorsm ! com>
Date: 1999-10-31 16:21:18
[Download RAW message or body]
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
>
Maybe simple to you ;-) It doesn't use Makefile.am, how do I do that?
Myself, David, and Simon all looked at it and are lost :(
> Greetings, Stephan
>
> --
> Everyone makes mistakes -- but we are more experienced at it
> anonymous KDE developer
--
Daniel M. Duley - Unix developer & sys admin.
mosfet@mandrakesoft.com
mosfet@kde.org
mosfet@jorsm.com
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic