octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Need test of patch for OS X


From: Ben Abbott
Subject: Re: Need test of patch for OS X
Date: Tue, 10 May 2016 19:00:08 +0000

> On May 10, 2016, at 11:24 AM, John W. Eaton <address@hidden> wrote:
> 
> On 05/10/2016 10:50 AM, Ben Abbott wrote:
> 
>> I did not modify octave.rb (the problems I saw occurred when building with 
>> Fink)
>> 
>> I checked the formula for Octave. There is a note to use the Java JDK from 
>> the link below.
>> 
>> https://support.apple.com/kb/DL1572?locale=en_US
> 
> Does it work if you have a current version of the JVM installed?
> 
> Currently, Octave's configure script is checking for the existence and 
> location of the JVM shared library.  And on OS X systems (only) the JVM is 
> linked with Octave and calls are made to JVM initialization functions 
> directly.  But the goal is to use the same method of dynamically loading the 
> JVM and calling the initialization functions through function pointers 
> (obtained from dlsym or an equivalent method).
> 
> Also, instead of only using the location of the JVM that is determined by the 
> configure script, I want to fix this so Octave finds the JVM at run time 
> based on things like JAVA_HOME or looking in the registry (on Windows 
> systems).  There should be no need for the JVM to be installed on the build 
> system.  Only the jni.h file, and, if building from the hg sources, the tools 
> necessary to compile .jar files.
> 
> jwe

I don’t think there is a standard JVM install for Mac OS X. Perhaps that is why 
OS X is handled differently?

Even so, I’d prefer that everything depend upon JAVA_HOME at run time. That 
would make it much simpler to tweak things and get Octave+Java to play nice 
with Mac OS X.

Ben





reply via email to

[Prev in Thread] Current Thread [Next in Thread]