On Monday 17. July 2006 19:46, Alexander Neundorf wrote: > On Monday 17 July 2006 18:33, Simon Hausmann wrote: > > On Monday 17 July 2006 18:02, Alexander Neundorf wrote: > > > On Monday 17 July 2006 00:12, Simon Hausmann wrote: > > > > On Sunday 16. July 2006 20:31, Thiago Macieira wrote: > > > > [...] > > > > > > > > > If you add a .o that happens to be in an ar archive into a shared > > > > > library, you've got a convenience library, not a static library. In > > > > > those cases, just link the .o once and for all. There's no need to > > > > > create the archive. > > > > > > > > Yes, but as long as the build system offers this feature people will > > > > use it. So I suggest that we either drop the feature alltogether or > > > > we use -fPIC there as well. But offering it as feature that only > > > > works on i386 when linked into a final shared object is not a good > > > > idea IMHO. > > > > > > Building convenience libs is not supported out-of-the-box by cmake. > > > What should we drop ? > > > > Well, STATIC seems to work out of the box as keyword for > > kde4_add_library. > > Ah, yes. > Do you think we should disable static libs for KDE4_ADD_LIBRARY() ? > I mean, it's prefectly ok to build a static lib as long as you don't link > it into a shared library.
And exactly that, as I tried to point out, happens all the time in KDE, since most of the targets in KDE are either shared libraries or kdeinit modules, both of which require -fPIC. Andras' mail on kde-core-devel is just another example of that as he hits /exactly/ this problem. Either we disable STATIC (and break the build) or we add -fPIC to the build flags (as suggested in my initial patch in this thread). My vote is on the latter, but ultimately I don't care as long as we solve it :) Simon
pgpoa1vZWrYs8.pgp
Description: PGP signature
_______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
