Re: Library packages, libtool and automake.
> Ahh, sorry. I just used dh_make and told it to debianize as a library.
> > Firstly, are you able to configure and compile it when doing so
> > directly (i.e., not via debian/rules)?
> Yes, that works fine.
> Yeah, this is what dh_make generated:
> ./configure --prefix=/usr
> -mkdir shared static
> # First build the shared library
> cd shared ; \
> $(MAKE) -f ../Makefile VPATH=".." srcdir=".." \
> CFLAGS="-O2 -fPIC -pipe" ; \
> gcc -shared -Wl,-soname,$(package).so.$(version_major) -o $(package).so.$(version) `ls *.o`
> Since this tries to link *.o into the shared library itself, this is why I
> assumed it's not going to work out-of-the box with libtool. Basically, I
> just need help getting the debian/rules right. :)
OK. I have never used libtool myself, but I would assume that if you
do, the code to generate the shared or static libraries ought to be
within the autoconf/automake input files? For example, the kpathsea
library autoconf has options --enable-shared, --enable-static. You
could perhaps look there to see how it's done. (In teTeX package.)
And your best bet is to find a package which uses libtool and see how
it does it. Or hopefully there'll be someone on this list who knows.
> > Perhaps you could post your configure.in, Makefile.am and debian/rules
> > for perusal if the above doesn't help? Or give a URL from where they
> > can be downloaded.
> Sure. Go to http://www.tailrecursion.com/libaccounting/
Sorry to not be more helpful :(
Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
Debian GNU/Linux Developer, see http://www.debian.org/~jdg