On Mon, Jan 13, 2003 at 06:12:59AM -0800, James Michael DuPont wrote: > *) Support for cross compilation > i think that it is important that we really come to terms with the new > configure tool. To be honest, i like the idea of using a perl based > configurator, and my research into autoconf and automake might feed > into this. > > How far do you plan on stepping on autoconfs toes with this? Do you > want to continue with a special solution, or does not it make sense to > turn around and go back to automake and autoconf?
Well, http://www.gnu.org/software/autoconf/autoconf.html says: Autoconf is an extensible package of m4 macros that produce shell scripts ... These scripts can adapt the packages to many kinds of UNIX-like systems Automake says (http://www.gnu.org/software/automake/automake.html): Automake requires the use of GNU Autoconf. which implies that autoconf needs a shell to run the configure system it generates. That's not going to work for Win32 (Not that I use Win32 personally, but I like things to work on Win32 because then no-one complains that things don't work, and so I can pretend it doesn't exist. I'm speaking personally here - other people working on parrot probably have much less selfish views on Win32) Or have I misunderstood all this? Nicholas Clark
