[Octave-bug-tracker] [bug #48678] mkoctfile returns linker flags on LFLAGS instead of LDFLAGS

[Mike Miller]

Follow-up Comment #5, bug #48678 (project octave):

Agree with jwe, I think it's important that mkoctfile treats CFLAGS, CPPFLAGS,
CXXFLAGS, LDFLAGS, etc as user variables that can be overridden from the
environment, and default to empty (in the case of LDFLAGS) or to a trivial
default (in the case of CXXFLAGS="-g -O2").

But do we want to append the built-in defaults to the user values and allow
the full set of flags to be exported? Or would that be too confusing?

For example could we combine the user's CPPFLAGS with what is currently called
INCFLAGS, and export that from "mkoctfile -p CPPFLAGS"? Same with user's
CXXFLAGS and XTRA_CXXFLAGS for "mkoctfile -p CXXFLAGS"?

Another enhancement might be to work on the naming convention of the built-in
compiler/linker options. It usually takes me a few tries of guessing to figure
out which of LFLAGS, OCTAVE_LIBS, DL_LDFLAGS, I need to export to build
something.
It might be a nice enhancement to work on the naming scheme for exporting the
default flags from mkoctfile.

    _______________________________________________________

Reply to this item at:

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

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