[Gllug] [OT] software packaging

[Thom May]

* Jonathan Dye (jonathan.dye at automationpartnership.com) wrote :
> > -----Original Message-----
> > From: James Hollingshead [mailto:james at hollo.org]
> > Sent: 29 May 2002 01:08
> > To: gllug at linux.co.uk
> > Subject: Re: [Gllug] [OT] software packaging
> 
> [...] 
> 
> > I normally start with just:
> > 
> > configure.in:
> >   AC_INIT(hello.c)
> >   AM_INIT_AUTOMAKE(hello, 0.0.1)
> >   AM_CONFIG_HEADER(config.h)
> > 
> >   AC_PROG_INSTALL
> >   AC_PROG_CC
> > 
> >   AC_OUTPUT(Makefile)
> > 
> > and Makefile.am:
> >   bin_PROGRAMS = hello
> >   hello_SOURCES = hello.c hello.h
> > 
> > and a bootstrap command of:
> >   aclocal && autoheader && automake --foreign --add-missing 
> > && autoconf
> > 
> > Overall I reckon simpler than doing it any other way, and if the
> > project expands it is easy to add to. My main wish is for a less
> > verbose syntax for adding in compile time options for ./configure.
> > 
> > James
> 
> 
> While we are talking about autoconf/automake I was wondering if anyone could
> recommend a good guide to these?
The automake/autoconf/libtool book is very good.
http://sources.redhat.com/autobook/
available online, via the cunning "online" link at that site.
Cheers,
-Thom, uncovinced that automake is a good thing, but in love with autoconf.

(oh, and once more the sigdaemon comes through with the goods ;) )

-- 
Thom May

<Jick> I use Automake for most of the projects I do 
<gstein> automake blows goats
<gstein> and after that, it goes and sucks off a few cows
<gstein> of course, before it buttrapes the monkeys


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug