[Octave-bug-tracker] [bug #49503] [mxe-octave] cross-building packages with configure script calling octave itself have issues

[Markus Mützel]

Follow-up Comment #23, bug #49503 (project octave):

The "build-octave" package uses the tarball MXE Octave was configured to use.
AFAICS, there's no need to have different flavors of that package.

Wrt the "hg-octave-dist" target, I was thinking about treating that the same
as an Octave installed on the build system. The same configure flags would
apply (either "--enable-system-octave" or "--disable-system-octave").

Adding some paths to the end of Octave's search path is a good idea.
Unfortunately, that wouldn't work for built-in functions. AFAICT, .m-file
functions (and .oct or .mex files) always shadow built-in functions no matter
where they occur in the search path.

If I understand the logic in the statistics of-package correctly, it uses
Octave only to check for functions existing in core Octave. IIUC, the only
Octave function that seems to execute in the build process is
"conditional_installation":
https://sourceforge.net/p/octave/statistics/ci/default/tree/utils/conditional_installation.m
Skimming through it, I don't see if it does anything else. Maybe John D could
add some insider info.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?49503>

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