Re: [Moose-g3-devel] Collaboration Tools, auto config

[Greg H. <gh...@ps...>]

Josef Svitak writes:
 > --- Hugo Cornelis wrote:
 > > In a more general context, a couple of other things we need are :
 > > 
 > > - configure as a unifying deployment interface to other developments,
 > > e.g. such that Genesis3 can be a subproject of another project or
 > > vice-versa.
 > > - again configure, such that we can deal with most of the portability
 > > issues for C/C++.
 > 
 > This is debatably the most critical piece missing from Moose at the moment. The
 > Autoconf family of tools is still the best choice for *nixes, including OSX.
 > For  Windows, I think the jury is out. We may be able to start with autoconf,
 > but CMake or SCons are more like choices.

I agree that configure is badly needed.  I am familiar with autoconf and
have written configure scripts before, so I might be able to contribute
to this.  Had anyone else already planned on writing a configure script
for MOOSE?   As far as Windows goes, I would favor a development environment
that is based on the Cygwin tools (which will give us autoconf, make, etc.).
with the understanding that the final executable should not require the
user to have Cygwin installed.
--Greg