Re: [octave-forge] (parallel) request help for testing at Windows

[Markus Mützel]

Am 25. November 2019 um 11:15 Uhr schrieb "Olaf Till":
> On Sun, Nov 24, 2019 at 11:55:08AM -0500, Nicholas Jankowski wrote:
> > octave:7> pkg load parallel
> > octave:8> test("__test_rfeval__.cc","verbose")
> > >>>>> c:\programs\octave\__test_rfeval__.cc
> > ***** test
> >  __test_rfeval__ (@ (x) sqrt (x), 1, @ (info, x) info.message);
> >  assert (__test_rfeval__ (9, 1, @ (info, x) info.message){1}, 3);
> >  assert (iscellstr (__test_rfeval__ ("a", 1, @ (info, x) info.message)));
> > open: No such file or directory
> > process generation failed
> >
> >
> > so far octave has been sitting at this state for a couple hours, windows
> > indicates all octave sub-processes at 0%
>
> Do I understand it correctly that Octave didn't return to the prompt
> after this? Even after hitting ENTER?
>
> Anyway, the problem seems to be that the default name of the Octave
> executable file or the path to this file is wrong. It occurs to me now
> that I didn't consider the '.exe' postfix of Windows... But for the
> case that it is not so simple, could you give me the following
> information, still:
>
> - From the Octave prompt, what does 'getenv("OCTAVE_BINDIR")' print out
>   (if anything)?

The batch files set up the environment variable "OCTAVE_HOME". That points to a 
directory that looks like the Linux root directory. That is, the binaries are 
located in 'fullfile(getenv("OCTAVE_HOME"), "bin")'.
In my case OCTAVE_HOME is "C:\Octave\Octave-5.1.0.0\mingw64".

> - From the shell, what does  'octave-config -p BINDIR' say? (Maybe you
>   must give the path to octave-config.)

PS C:\Octave\Octave-5.1.0.0\mingw64\bin> .\octave-config.exe -p BINDIR
C:\Octave\Octave-5.1.0.0\mingw64\bin

> - In the directories, if any, printed out by the above, what are the
>   filenames of the Octave executables? Is there an 'octave-cli.exe'?

Yes, there is. But it is recommended to call the batch files instead. Just 
calling "octave" should be correct unless you want to specifically omit setting 
up the correct environment.
Once Octave is running, the "bin" directory is in the path:
>> system("octave-config -p BINDIR")
C:\Octave\OCTAVE~1.0\mingw64\bin
ans = 0
>>

HTH,
Markus