Re: Help with SHARED_LIBS

On Mon, Jun 21, 2021 at 06:17:56PM +0100, Stuart Henderson wrote:
> On 2021/06/18 01:15, Hannu Vuolasaho wrote:
> > Hello everyone!
> >
> > I'm trying to make a port of Ringdove pcb tools (pcb-rnd, camv-rnd)
> > and I'm working with the needed common part librnd.
> >
> > Currently I'm stuck in SHARED_LIBS. How should I manage the versions?
> > Ringdove programs don't use libtool and currently I have in my PLIST
> > for example
> >
> > @so lib/librnd-poly.so
> > lib/librnd-poly.so.3
> > @bin lib/librnd-poly.so.3.0.0-dev
>
> Only one of these files should be created, it should be named
> (initially) librnd-poly.so.0.0 and appear in the PLIST as
> @so lib/librnd-poly.so.${LIBrnd-poly_VERSION} - the version number
> needs to be under control of the SHARED_LIBS line in the port.
>
> Marc Espie wrote:
> > Stuff that doesn't use libtool or cmake or similar framework will tend
> > to do things by hand, sorry.
> >
> > In general, patching the Makefile (or equivalent) to use the correctly
> > named variables is the way to go.
> >
> > see bsd.port.mk(5) for the variable name
> >
>
> ..
>
> > In the case at hand, grepping for soname will put you on the right track
> > for finding the Makefile that needs patching.
> >
> > (I had a look at the INSTALL... I wish you good luck. Most software that is
> > so GNU-centric that they say "you need make" when they obviously mean
> > "gnu-make" is probably going to be heaps of fun to port)
>
> grepping for "LIB.*_VERSION" in the ports tree might show up something
> borrowable too.


I should add that very often, getting that stuff right is not the most
difficult thing about porting stuff.

If you end up having ports that work, fixing SHARED_LIBS ought to be the
easiest part or so.

You will often need to fight a bit over the configure/Makefile bits, as
non-standard stuff also tends to do shitty stuff like mixing up build/install,
using the network during build, or installing directly in weird directories
and not heeding DESTDIR.

But if you manage to get basic shitz working, you will most probably find
help with the remaining infrastructure bits by sending a half-done port.