Re: automake --no-force (Was: autoreconf invode automake with --no-force (autoconf ver.2.54))

[Nishio Futoshi]

Thank you for your reply, and I understand that.


I think that we can use `autoreconf' for bootstrap.  We don't have to
invoke `aclocal', `automake', `autoconf', and `libtoolize' separately,
even if one uses Autotool for the first time with the package.  Now we
can do that, `autoreconf --symlink --install --force'.

We still have to write `configure.in(ac)' and `Makefile.am' by hand.
However, `autoscan' works fine, ans writing `Makefile.am' is easier
than writing `Makefile' or `Makefile.in'.


My suggestion for beginers:

Use autoscan in your source directory, then rename `configure.scan' to
`configure.in'.  Then edit `configure.in'.  Your works are to modify
`AC_INIT' arguments, comment out `AC_CONFIG_HEADERS', add
AM_INIT_ATOMAKE([foreign]), and modify AC_CONFIG_FILES([Makefile]).
And create `Makefile.am'.  First line is `bin_PROGURAMS =
packagename', and second line is packagename_SOURCES = yoursource.c
yourheader.h ...'.  Then run `autoreconf -sif'.  Does that sound
difficult?

Unfortunately, it's not for portability, but I think it's a good
tutolial for beginers.  They can stand on start line for using
Autotool.

Thanks

-- 
Nishio Futoshi <address@hidden>