A little review of kdecore & kdeui
neundorf at kde.org
Sat Apr 8 09:09:30 BST 2006
On Saturday 08 April 2006 10:00, Simon Hausmann wrote:
> On Saturday 08 April 2006 09:40, Alexander Neundorf wrote:
> > On Saturday 08 April 2006 09:36, Simon Hausmann wrote:
> > > On Thursday 06 April 2006 01:21, Thiago Macieira wrote:
> > > > >But I thought it wasn't possible to link a static lib into a shared
> > > > > lib?
> > > >
> > > > It isn't.
> > >
> > > What is the problem with that? Why can't we support that if we always
> > > compile static libraries PIC? (just as we did in KDE3 with libtool)
> > >
> > > Or is it the problem of --whole-archive?
> > It is unportable and not longer required with cmake.
> We could indeed as David suggested install sources for classes that we
> don't want in shared libraries yet, classes for which we don't want to
> promise binary compatibility yet. But that is certainly not as convenient
> in usage in applications as linking against a library.
> What exactly is the problem with compilling them into a static library?
> What exactly do you think is unportable?
Although I'm currently something like the buildsystem guy, I don't feel like
Well, everwhere where it's used there are big comments that it's unportable to
link static libs into shared libs.
Usually only the symbols which are used are pulled in the shared lib, but for
some/most/all (?) linkers exist some special flags which cause it to pull in
the complete static lib.
I guess other developers know more details.
Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org - http://www.kde.org
alex AT neundorf.net - http://www.neundorf.net
More information about the kde-core-devel