|
From: | Michael D. Godfrey |
Subject: | Re: Release Plans |
Date: | Mon, 22 Apr 2013 22:25:13 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 |
On 04/22/2013 10:02 PM, Mike Miller wrote:
This fixed dependence will surely cause trouble. For various reasons the versionFor the Java experts: Octave currently compiles in the JAVA_HOME path at build time. This means a user of a binary Octave package has to have the same version of Java installed in the same directory as the maintainer who built it, right? Is it possible to compile against the JNI and load any JRE at run time from JAVA_HOME and test it for features? In other words, would it be possible to build Octave with JAVA_HOME=/usr/local/java-1.6.0 and run the resulting Octave binary on another system with JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-amd64?
of Java may be updated, and then the Octave interface breaks. It will be much better to implement the JNI interface and test for the version of Java at runtime. Will this work fairly reliably? Michael
[Prev in Thread] | Current Thread | [Next in Thread] |