Kelly O'Hair wrote:
For Linux and Solaris I could see such a thing, even with all the
different Linux variations. But Windows... :^(
You could restrict it to Windows&CYGWIN and starting from a cygwin shell,
but I suspect that would not be satisfying all the Windows users.
There are Windows&MKS and possibly Windows&OtherUnixToolSet, and
would you need a configure.bat ??? :^(
Well... we could start with the currently supported platforms
(cygwin/mks) and then if someone else wants/needs to build with a
different unix toolset, they'd have to create the configure script for
that. We could start small.
The fact that the JDK Makefiles want a fullpath to each tool makes
life difficult,
see
http://hg.openjdk.java.net/jdk7/build/jdk/file/tip/make/common/shared/Defs-utils.gmk
I understand why this was done, and maybe this also was part of the
sanity issue around tools (the path to the specific tool being exact
provided a minor sanity check?).
Maybe the configure script creates this file for the Makefile system?
Yeah, that's kinda what I was thinking.
In the long run I do think we need a configure step, just not sure
when it could be done, or how far you want to take it.
I think the hardest thing would be establishing the process. Once we
have a configure script, we could slowly migrate things out of the
makefiles and into it for the things it makes sense to do.
--
- Keith
