Re: [MinGW-dvlpr] Updated configure scripts in mingw and w32api

[Keith M. <kei...@us...>]

On Wednesday 24 May 2006 6:18 pm, Christopher Faylor wrote:
> I just updated the configure scripts in mingw and w32api to use
> autoconf 2.59.  This was required for some work that is being done in
> the winsup parent directory.
>
> I hope that this won't cause any problems.  It seems to work fine but I
> had a fair number of problems getting this working.

I'd be surprised if we see any problems resulting from this; I've been 
using autoconf 2.59 quite happily, under MSYS, for at least a year, and 
probably nearer to two, now.

> Have I mentioned that I hate autoconf/libtool/automake?

Yeah.  In in response to a rant of mine, on the subject of automake :-)

I've never used libtool, so can't comment on it.  One excursion into the 
world of automake was one too many; I too find it utterly abhorrent.  I 
do quite like autoconf though, subject to the following gripes:

1) I don't like it when developers stuff rafts of shell script into 
configure.ac; this should be encapsulated into macros, and belongs in 
aclocal.m4, IMHO.

2) The caching feature is quirky; its interaction with AC_PATH_PROG and 
AC_PATH_TOOL in particular, is just plain broken, IMHO, but suggesting 
that this is so seems to attract much vitriolic criticism on the autoconf 
mailing list.

On the whole, I prefer to see an autoconf generated configure script, 
than one which has been hand crafted, because the developer says it is 
too much effort to use autoconf.  Sure, the autoconf generated script 
*looks* untidy, but it does usually work, and is portable; (and of 
course, once you've learnt to use autoconf, it *is* easier and quicker 
than hand crafting); I've *never* encountered a hand crafted script which 
comes close, in the portability stakes -- most work only on one platform, 
which just happens to be what the original developer was working on.

Regards,
Keith.