building static libs

[Paul Smith]

My ISP appears to get this sort of treatment regularly.  I just don't
have the time or energy to investigate or switch to something else.  I
know that's why they can probably get away with it, but... that doesn't
give me more time or energy :p

On Tue, 2020-11-03 at 00:16 +0100, Mark Wielaard wrote:
> To be honest I recently removed the static development libraries from
> Fedora since nobody was using the (and the only package that
> dependent on them did so by accident). And was hoping to eventually
> remove the static builds from the code.

In the environment I have set up each package is deployed in its own
subdirectory, in a 100% relocatable configuration (the entire structure
is checked into source control and users can check it out anywhere they
want and it must work).  The repository contains versions of some tools
for Linux, Mac, Windows (of course things like GDB etc. are only in the
Linux section)  I prefer to avoid symlinks as they are not well-
supported on all platforms.

While I can conceivably figure out how to use an RPATH to get GDB to
find the libdebuginfod shared library in its project-specific location
via relative paths, it's just simpler all around to link statically.
 The advantages of shared libs aren't really compelling to me in this
configuration.

Hopefully they won't go away, but I guess that's up to you folks!