[Octave-bug-tracker] [bug #48671] Windows mkoctfile does not substitute Octave installation path correctly

[John Donoghue]

Follow-up Comment #8, bug #48671 (project octave):

Found the issue in w32_get_octave_home in shared-fcns.h:

For Windows, if the OCTAVE_HOME env string is not set, It is getting a list of
running modules and looking to see which one has octave in its name and using
its module path.

For mkoctfile of course, the name isn't 'octave'.

How about using the running modules full path/name using GetModuleFileName [1]
and extracting the path ?


Patch attached.

[1]
https://msdn.microsoft.com/en-us/library/windows/desktop/ms683197(v=vs.85).aspx


(file #39369)
    _______________________________________________________

Additional Item Attachment:

File name: bug48671.patch                 Size:1 KB


    _______________________________________________________

Reply to this item at:

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

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