[Octave-bug-tracker] [bug #61905] Build fails when using slibtool instead of GNU libtool

[Markus Mützel]

Follow-up Comment #27, bug #61905 (project octave):

> Unless you're targeting systems from the early 90s, $(CC) <whatever> works
fine and gives you only the file you want in the place you expect.

Is it possible to write those rules in a way that works correctly across
different platforms and compilers (GCC, clang, Apple clang, Intel C++, IBM,
...)? (We definitely don't have the resources to test that reliably.) Isn't
that the reason something like `libtool` exists in the first place?

> IMO this is a lesser evil and a bargain for removing the .la file parsing
from the install-oct target.

I agree that parsing the .la file might not be the best solution. But I'm not
sure which approach would be the better one in the long run: Relying on the
layout of the .la file, or implementing and maintaining build rules for the
different combinations of compilers and platforms ourselves instead of relying
on tools like `libtool`?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61905>

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