On Sat, Mar 30, 2024 at 08:02:18PM +0100, Sven Joachim wrote:
> On 2024-03-30 12:38 +0100, Santiago Vila wrote:
>
> > El 30/3/24 a las 9:43, Sven Joachim escribió:
> >> I think it would make sense for Debian to follow what Arch and Fedora
> >> are doing, introduce a libdialog15 package with the shared library and a
> >> libdialog-dev package with the .so symlink but without libdialog.a,
> >> because that requires (if I understood you correctly) configuring and
> >> building dialog twice, greatly complicating packaging.
> >> Santiago, do you think this is a good plan?
> >
> > Yes. If we can avoid the static library to keep it simple, that would be
> > better.
> >
> > Simple question: Is that really allowed these days? I wanted to be sure
> > by reading Policy but did not find any statement saying they are required
> > or not.
>
> I could only find the following two sentences in §8.3:
>
> ,----
> | The static library ("libraryname.a") is usually provided in addition
> | to the shared version. It is placed into the development package (see
> | below).
> `----
>
> So shipping static libraries is recommended but not required, and there
> are certainly quite a few packages where upstream does not support them.
> But see below.Actually, for development on MacOS, I have to use static libraries, because there's no useful analog for LD_LIBRARY_PATH :-) > >> I can work on an updated patch. > > > > That would definitely help. > > This afternoon I got my hands dirty. The first attempt to simply pass > --with-shared to configure failed to give me a libdialog.a, and it also > produced the following odd collection of *.so* files: > > libdialog.so -> libdialog.so.15.0.0 > libdialog.so.1.3 > libdialog.so.15.0.0 -> libdialog.so.1.3 fwiw, ncurses, dialog and cdk use the same scripts (and version information) > Not what you would expect, and it does not match the files shipped in > the Fedora and Arch packages. A closer look revealed that they both > configure dialog --with-libtool, and that worked great because it gave > me not only the expected layout of *.so* files, but also a static > libdialog.a library. :-) perhaps - but since aside from Linux, libtool support is not reliable, it's not going to be of primary concern to me. -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net
signature.asc
Description: PGP signature
