[Debichem-devel] [Debichem-commits] r847 - in /wnpp/avogadro: ./ debian/ debian/avogadro.install debian/changelog debian/compat debian/control debian/copyright debian/libavogadro0-dev.install debian/libavogadro0.install debian/rules

[Michael Banck]

On Tue, Nov 13, 2007 at 09:35:45AM -0800, Jordan Mantha wrote:
> On Nov 13, 2007 8:35 AM, Michael Banck <mbanck at debian.org> wrote:
> > On Mon, Nov 12, 2007 at 03:02:14AM +0100, Daniel Leidert wrote:
> > > IMHO here we (again) should decide, if we want to ship the library and
> > > the -dev package or if we should simply statically link it into
> > > avogadro.
> >
> > Agreed, I think we should try to not to get too many library packages
> > introduced; avogadro looks like an end-user application to me, so
> > libavogadro might be the exposure of some internal implementation rather
> > than meant for outside developers?
> >
> > If other project start to use libavogadro then of course we should ship
> > it.
> 
> Kalzium 4.1 will be using it for sure. That's quite a while off yet
> but it's simpler packaging to "do the right thing". We can do a
> convenience library like we did for gchempaint but I have no idea how
> to do it with cmake, that the big reason I split it up.

Well, you can't; cmake doesn't support it.  Best you can do (according
to the cmake FAQ, I went through this for another package last week) is
manually adding all the [libavogadro] sources to all the objects which
would statically link the libavogadro.la convenience library.

So OK, if Kalzium uses it, I guess it's fine.


Michael