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

[John W. Eaton]

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

Looking at it now, mkoctfile has variables like RANLIB, AR, CXX, CXXFLAGS,
etc., that it uses and that the user could override if needed.  Having
"mkoctfile -p CXX" display that variable is useful as a way of saying "this is
the default for the C++ compiler that mkoctfile will attempt to use".  But
there is, of course, no guarantee that these things will exist on the system
where mkoctfile runs.

It seems to me that the other variables like the version and installation
directories also really only make sense as read-only configuration variables. 
Most of these are currently only in octave-config.  Probably we should make
some distinction between variables that users may override and which are for
informational purposes only.

The FFTW3 variables should probably just be removed.  Is there any
justification for keeping them?

Should we keep system-wide variables like BINDIR, EXEEXT, MANDIR, MAN1DIR,
etc.?  I don't see why, if we are not providing info about things like FFTW,
HDF5 or PCRE.

    _______________________________________________________

Reply to this item at:

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

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