cmake 2.6.2 now required - changes in handling shared libs
Ben Boeckel
mathstuf at gmail.com
Fri Nov 28 23:27:13 CET 2008
On Friday 28 November 2008 16:43:07 Alexander Neundorf wrote:
> On Friday 28 November 2008, Ben Boeckel wrote:
> > On Thursday 27 November 2008 15:02:54 Alexander Neundorf wrote:
>
> ...
>
> > > Exporting targets is only useful if you install shared libs which
> > > should be used by other projects. Is that the case for you ?
> > >
> > > Alex
> >
> > Sigcore is a shared library that is also in my project. It's a game
> > engine, so it may or may not me used by other projects, but if it is,
> > these libraries handle the loading and saving of the game data. The
> > sigcore and sigmod directories are siblings, so I'm not sure how to
> > export the sigcore target without installing sigcore (or hacking around
> > to find where the
>
> Why don't you want to install sigcore ?
> You install sigmod, and sigmod seems to link to sigcore, so you should also
> install sigcore.
>
> Can you please explain a bit more ?
>
> Alex
I'm upstream; installing for every library would be counterproductive. I'd have
to do `make sigcore; make install sigcore; make sigmod; make install sigmod` and
so on for each library. I want to just be able to do `make` and have everything
work as it did before I tagged things with exports.
--Ben
More information about the Kde-buildsystem
mailing list