Re: [naviserver-devel] new vfs changes 2

[Stephen D. <sd...@gm...>]

On 10/10/05, Zoran Vasiljevic <zv...@ar...> wrote:
>
> Eh... needles to say that I do not really understand all this autoconf
> machinery. I was used to make a configure.in and hit autoconf. Now it
> seems that all gotten much more complicated. For example, when do I
> need acinclude.m4? Do I make it by hand or somebody is creating this
> for me? What about aclocal.m4? I used to edit this by hand, it gets
> created now automatically? What I miss (in order to better understand)
> is a birds-eye view on the build machinery: what I need to supply by
> hand and what is automatically created and what I have to run in order
> to get those automatically created). Do you happen to have some info
> on that?


(Sorry this took a while...)

I dropped acinclude.  All autoconf macros additional to those that
ship as standard with the autoconf package now go in the m4 directory,
whether written by ourselves (dns.m4) or imported from other sources
(tcl.m4).

People who build from tarballs run configure, make, make install, as before=
.

People who build directly from cvs run autogen.sh, make, make install.

The autogen.sh script creates aclocal.m4, uses that and configure.in
to create configure, then runs it.  We no longer keep the configure
script in cvs, as it can be regenerated.  This shouldn't be a problem
in 2005 with all unix like OS shipping with the autotools.