[Octave-bug-tracker] [bug #54260] mkoctfile doesn't export some Octave features that packages need at build time

[Mike Miller]

Follow-up Comment #2, bug #54260 (project octave):

Agree with all of your points, especially about not using Octave to get
features needed. But do you mean that for HDF5 for example, should a package
use its own configure logic, or should HDF5 flags be added to mkoctfile for
packages to use?

I think octave-config was meant to be analogous to other -config programs,
(fltk-config, pcre-config, mysql_config, etc) to just report any information
that might be useful to someone who wants to build against Octave. mkoctfile
started out as just a compiler wrapper, but over time it has added more
variables that might be useful, so there is some overlap now.

My preference would be to move more into mkoctfile as needed, and deprecate
octave-config, so there is one tool that does everything needed for building
something against Octave. But I don't have a strong opinion about whether
mkoctfile should report PCRE_LIBS and HDF5_LIBS, or whether packages should
write their own configuration logic using autoconf for those.

    _______________________________________________________

Reply to this item at:

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

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