automake and ./configure (was: installation paths, option definition)

[Neil Williams]

On Saturday 03 September 2005 10:42 pm, Christian Stimming wrote:
> > True. The one advantage is that it builds under a "make" - it does not
> > require another ./autogen.sh - it can be a significant advantage during
> > development of the associated files because you then only make that
> > specific file. autogen takes FAR longer.
>
> Not true. Don't you use "--enable-maintainer-mode"?

Yes, autogen.sh enables it every time.

> > > 4. Add the resulting *output* file in that directory's Makefile.am to
> > > any variable that ensures that this file is distributed, e.g.
> > > noinst_HEADERS=qsf-dir.h and probably also BUILT_SOURCES=qsf-dir.h
> >
> > You lose the ability to re-create the file with 'make'.
>
> No. --enable-maintainer-mode will do exactly that.

Hmm. Anyway, it's changed now.

> > > I don't quite understand why the manual rule was added in the first
> > > place.
> >
> > Because it's powerful during development - FAR more useful than putting
> > it AC_OUTPUT.
>
> No. The other way round.

That's not how it's seemed in the past - ne'er mind.

-- 

Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20050903/c609198e/attachment-0001.bin