Steven Augart wrote:
> > How about including all the build options in the Configuration class?
> >
> > public class Configuration {
> > public static final String BUILD_OPTIONS = {
> > "--enable-jni", "--enable-load-library", ...
> > };
> > ...
> > }
> Perhaps we could include even the build options that automatically had
> their default values set? So, even if the user had not explicitly
> stated "--enable-jni", we would still include "--enable-jni", since
> it's the default?
>
> I'm trying to guard against the defaults possibly changing. If we
> were to, for example, one day make Classpath's default be
> --enable-portable-native-sync, I'd still want Jikes RVM to correctly
> read that the Classpath installation had that feature enabled.
Agreed.. in general more info is better. E.g., why not also throw in
the output of "uname -a", the classpath version, etc.
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
