[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51919] environment variable OCTAVE_JAVA_DIR
From: |
Ernst Reissner |
Subject: |
[Octave-bug-tracker] [bug #51919] environment variable OCTAVE_JAVA_DIR |
Date: |
Wed, 13 Sep 2017 16:38:06 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 |
Follow-up Comment #5, bug #51919 (project octave):
I have another aspect: the directory under consideration
is called initial_java_dir in the code in ov-java.cc.
Thus I call it here initial java dir.
If you have a look in the code (initial_class_path),
it plays *three* roles:
* where octave.jar resides which is the initial section of the classpath
* where the file javaclasspath.txt resides which defines the installation wide
portion of the classpath which comes after the project wide and after the
user-wide one.
* where the file java.opts resides containing the (installation wide) options.
All these three files must be moved if the initial java dir is changed.
I think it is easy to document this:
If OCTAVE_JAVA_DIR is not set, this is the directory
where javaaddpath.m resides
which can be found out by 'which javaaddpath'
Otherwise, the java directory is given by OCTAVE_JAVA_DIR.
Then one has to document the three roles and that's it.
In further steps, we can try to improve this,
but i think the first step would be to add this piece of information to the
documentation.
I would like to prepare a patch if you agree.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51919>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/