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

[Mike Miller]

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

I think we could talk about what the right solution for a future release of
Octave could be. I know this was touched on at least a bit when we made the
move to deprecate octave_config_info. There are certain feature tests that
some Forge packages need to perform in their configure scripts.

The image package needs to run a native octave process to query whether the
"im2double" function is implemented in Octave itself, so that it can either
provide its own implementation or not. This kind of thing is a temporary
measure until it can do a hard dependency on the Octave 4.2 release for
example.

The communications package runs a native octave to query the options that
Octave has for building against HDF5 (HDF5_CPPFLAGS, LDFLAGS, etc), which are
not available via a cross-mkoctfile tool. This could be done differently, by
querying for HDF5 itself rather than relying on Octave for how to (and whether
or not to) build against HDF5.

    _______________________________________________________

Reply to this item at:

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

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