[Octave-bug-tracker] [bug #48671] Windows builds contain references to invalid paths

[Mike Miller]

Update of bug #48671 (project octave):

                Category:                    None => Configuration and Build
System
              Item Group:                    None => Incorrect Result       
                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

Thank you for your bug report. The existence of strings referring to these
invalid paths is not in itself a bug. Octave is cross-compiled, and as far as
I can tell it will continue to have these references embedded in it as long as
it is built this way. However, as long as the OCTAVE_HOME environment variable
is set correctly, most things should work.

Does deleting the .la files allow the build of your external project to work?
Maybe they should be deleted from the installer.

The difference between octave-config and mkoctfile is curious, they should
both be substituting the path to where Octave is installed, if I'm reading the
code correctly. Does setting OCTAVE_HOME fix mkoctfile? Is OCTAVE_HOME set
when you call one but not the other?

    _______________________________________________________

Reply to this item at:

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

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