The next configure schema? [was: missed aprutil.make file]

["William A. Rowe Jr." <wr...@rowe-clan.net>]

On Sun, 10 Mar 2013 23:41:39 -0500
"William A. Rowe Jr." <wr...@rowe-clan.net> wrote:

> The right solution is to export them using the (portable) scons or
> cmake.  My own preference is cmake, which I've worked on quite a bit
> in the past couple years.  Paul introduced a partial scons solution
> to the trunk of the apr build schema.

My thinking on cmake devolves to this; it (almost) creates entirely
usable nmake files for simplistic windows builds with no target
platform knowledge, from either unix or windows.  For those on GUI,
it futher creates most any studio environment project files.  And it
has good solutions for unix platforms as well.  An scons user is most
welcome to speak to these points.

I don't think we are discussing 'dropping' autoconf at this point,
since most platforms need the 'tool' (scons or cmake) installed
to solve their build.  But compared to endlessly downloading
autoconf gunk, and the vargarities between released autoconf 
versions and their resulting configure scripts, the simplicity 
of scons or cmake is very appealing in the long haul.