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

[Markus Mützel]

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

> Do you have any idea about the best way to accomplish that?
Well, you could parse the .la file... 😉

I'm attaching one of the .la files from the Windows build just in case.
Afaict, it's the `lnames` read from the line starting with `library_names=` in
the old/current rule.

More seriously: I don't know of a cross-platform way to get that info.
`libtool` hides all of that usually. But it's different in this case
unfortunately.

IIUC, the extension for import libraries might be different on Windows
depending on whether the library is built with a mingw/GCC-toolchain or with
MSVC (`.lib`?). Even if I don't know of anyone is currently building Octave
with MSVC, hard-coding `.dll.a` probably isn't a good idea either...


(file #52820)
    _______________________________________________________

Additional Item Attachment:

File name: __delaunayn__.la               Size:1 KB
    <https://file.savannah.gnu.org/file/__delaunayn__.la?file_id=52820>



    _______________________________________________________

Reply to this item at:

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

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