[EMAIL PROTECTED] wrote:
Jean-Frederic,
I personally would rather see the Makefile pick up
the $(JAVA_HOME) environment variable instead
of the configuration shell script. By doing it this
way, you don't have to run the configuration again
when or if JAVA_HOME changes, lest the result
be a mixture of two JDK versions. Does this make
sense?
My idea is to use autoconf... In this case it is very easy to redo
configure: "./configure --with-java=$JAVA_HOME2 ..."
Of course the JAVA_HOME have to be in a .in file included in Makefile
for example Makedefs.in
+++
[EMAIL PROTECTED]@
+++
The problem in the current config.sh is that it contains a Makefile
syntax in a shell script...
Dan Lydick
-----Original Message-----
From: Jean-frederic Clere <[EMAIL PROTECTED]>
Sent: Oct 30, 2005 12:56 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [BootJVM] configure
I have an additional correction for config.sh:
+++
[EMAIL PROTECTED]:~/harmony/enhanced/trunk/sandbox/contribs/bootjvm/bootJVM>
svn diff config.sh
Index: config.sh
===================================================================
--- config.sh (revision 329310)
+++ config.sh (working copy)
@@ -1656,8 +1656,8 @@
# Set up include path for the current tree, the configuration,
# the JVM tree, and the JDK tree.
-JAVA_INCLUDE_PATHS="-I$(JAVA_HOME)/include \
- -I$(JAVA_HOME)/include/$osJDKdir"
+JAVA_INCLUDE_PATHS="-I$JAVA_HOME/include \
+ -I$JAVA_HOME/include/$osJDKdir"
USEDOX="for 'dox.sh' and 'gmake dox'"
USEBLDCLN="for 'gmake all' and 'gmake clean'"
+++
Cheers
Jean-Frederic
Dan Lydick
