[Octave-bug-tracker] [bug #53938] windows octave doesnt wait for to --eval statements to complete

[John Donoghue]

Follow-up Comment #2, bug #53938 (project octave):

yes to the last part of the comment with the OCTAVE=, which is really the
issue I was trying to communicate on the bug report :).

Doing a pkg install calls configure_make.m, which sets the variables that
configure and make will use:

cenv = {"MKOCTFILE"; mkoctfile_program;
            "OCTAVE_CONFIG"; octave_config_program;
            "OCTAVE"; octave_binary};

where octave_binary = fullfile (octave_bindir, sprintf ("octave-%s%s", ver,
ext));

and then for configure:

cmd = ["cd '" src "'; " scenv "./configure " flags];

and for make:

sprintf ("%s make --jobs %i --directory '%s'", scenv, jobs, src)


So anyone writing a makefile that takes notice of the OCTAVE value, will be
using octave-4.0.0, rather than octave-cli.


For the make octave.bat call 'octave-cli.exe' o=comment, I'm fine with that -
cmdshell.bat should probally also be updated to include the base install path
in its path so that octave.bat will be found from the command line.

    _______________________________________________________

Reply to this item at:

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

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