|
From: | Steven Augart |
Subject: | Re: Configuration class and --enable-native-sync |
Date: | Tue, 06 Apr 2004 17:51:01 -0400 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 |
Archie Cobbs wrote: [...]
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?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", ... }; ... }
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.
--Steve -- Steven Augart Jikes RVM, a free, open source, Virtual Machine: http://oss.software.ibm.com/jikesrvm
[Prev in Thread] | Current Thread | [Next in Thread] |