octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #54219] Dynamic detection of JVM on macOS


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #54219] Dynamic detection of JVM on macOS
Date: Sun, 1 Jul 2018 17:47:19 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Follow-up Comment #1, bug #54219 (project octave):

What do you think about the following ideas?

* Combine this effort with bug #40111, meaning a patch or series of patches
that addresses JAVA_HOME detection on all Unix and GNU systems?
* Use an m-file function callback to do the filesystem logic part of deriving
the full file name of the libjvm.so/libjvm.dylib from JAVA_HOME? See for
example the m-file code I posted at bug #40111.
* Separate the library reorganization aspects / new functions necessary, if
they are necessary, from the Java changes as distinct changes.

What version of Java are you testing with? Does Java on macOS still have a
"$JAVA_HOME/jre/lib" directory? On GNU/Linux that is now just
"$JAVA_HOME/lib".

Is /usr/libexec/java_home a hard-and-fast well-known name that will never
change? Is there some other way to encode or configure the location of that
helper command? Should macOS users just have a system initialization octaverc
file that calls that command and sets the JAVA_HOME environment variable?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54219>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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