[Octave-bug-tracker] [bug #40111] support runtime selection of Java with JAVA_HOME on Linux and Unix systems

[Philip Nienhuis]

Follow-up Comment #28, bug #40111 (project octave):

@Mike comment #24:
_ if bin/client is found, it should prefer that to bin/server_
At one time I had a 32-bit and a 64 bit Octave plus 32-bit and 64-bit Java
installed, and *AFAIR* both Octaves accessed the proper (bitwidth) Java
installation w/o any issue or JAVA_HOME environment settings (the latter don't
exist on Windows by default).
Hopefully linking preferrably to ./bin/client doesn't break that (..)
(IIRC some bitwidth/Java discussion has happened a few years back, also
related to ./client vs. ./server, there may be some clues in that discussion)

And that's not just Octave; I have 32-bit and 64-bit Java installed as I have
a mixture of 32-bit and 64-bit SW that uses Java like GIS clients,
LibreOffice, Freemat at one time,etc. AFAICS all that SW automagically links
to the "proper" Java installation.
(BTW not that I'm a Java fan, but mentioned SW Just Works and fulfills our
needs)


    _______________________________________________________

Reply to this item at:

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

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