Re: Library packages, libtool and automake.

["Marcelo E. Magallon" <mmagallo@efis.ucr.ac.cr>]

On Tue, Jun 08, 1999 at 01:20:08AM +0100, Julian Gilbey wrote:

> >         ./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?

yes.  libtool generates both the shared and the static libraries on a single
pass, on the same directory.

./configure --prefix=/usr
make

that should be enough.

In fact,

	libtoolize --force --copy
	autoconf
	automake
	./configure --prefix=/usr
	make

should be able to build everything from just the Makefile.am and
configure.in files (and the sources, of course).  The first three steps are
not necessary unless you modify the Makefile.am/configure.in files, IIRC.



		Marcelo