[Octave-bug-tracker] [bug #44370] Octave compiler flags used at build time are not used by mkoctfile

[Mike Miller]

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

It's worth noting that flags in the user's CPPFLAGS and LDFLAGS (as well as
CFLAGS and CXXFLAGS) are represented in mkoctfile. So a workaround that I
think should work would be to build Octave like this:


$ ../configure CPPFLAGS=-I/usr/include/hdf5/serial
LDFLAGS=-L/usr/lib/x86_64-linux-gnu/hdf5/serial


instead of like this


$ ../configure --with-hdf5-includedir=/usr/include/hdf5/serial
--with-hdf5-libdir=/usr/lib/x86_64-linux-gnu/hdf5/serial


And when bug #43180 is fixed this should no longer matter, because hdf5.h
won't be part of the Octave public API anymore. I don't know if this same bug
exists for other external libraries (fftw, suitesparse, etc). At some point I
would like to clean up the Octave API and ensure that we're not including
things that don't need to be part of the interface.

So it's only the library-specific options that are not passed on to build
every oct-file that the user might want to build. I think this is correct,
frankly, because I shouldn't have to build my oct-file against hdf5 and fftw
and suitesparse and arpack and ... if I don't use any of their functions.

I'm not saying we shouldn't fix this, but we should be cautious that we don't
force unnecessary include and link dependencies on a simple hello-world
oct-file.

    _______________________________________________________

Reply to this item at:

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

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