[Octave-bug-tracker] [bug #41296] build mkoctfile and octave-config as executables on all platforms

[Mike Miller]

Follow-up Comment #15, bug #41296 (project octave):

Rik: only when running from inside of Octave, but these can be run from Forge
package configure scripts or Makefiles.

Thanks for cleaning that substitution code up. Here are the differences
between the old and new that I see now with this change. These are probably
good changes, just noting the slight differences now in case it does affect
somebody.


$ unset OCTAVE_HOME
$ mkoctfile-old -p OCTAVE_HOME
# empty string
$ ./src/mkoctfile -p OCTAVE_HOME
/opt/gnu/octave
$ export OCTAVE_HOME=/foo
$ octave-config-old -p PREFIX
/foo
$ ./src/octave-config -p PREFIX
/opt/gnu/octave


So in other words, octave-config now keeps PREFIX to the compiled-in
directory, it used to substitute OCTAVE_HOME into the PREFIX variable as well.
And mkoctfile now prints the value of PREFIX when OCTAVE_HOME is requested but
it is not in the environment.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/