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

[John W. Eaton]

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

Yes, octave-config was meant to be like those other -config programs.  That
was a popular thing to do before pkg-config emerged as a crowd favorite.  We
could also provide a pkg-config file for Octave.  That can also be used for
cross compiling, correct?

Either way, as a first step we could certainly eliminate the duplication by
deprecating octave-config and having mkoctfile do everything that
octave-config currently does.

For Octave dependencies, there is no way to guarantee that the dev libraries
and tools are available just because they were available on the system where
Octave was built.

But we could put our configure checks in separate .m4 files and distribute
them so that people can easily use the same tests we do in Octave.


    _______________________________________________________

Reply to this item at:

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

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