(imo,
the example of non-PIC assembly is a bit of a reach these days)
Probably true, that was just the first reason that came to mind; there are others for why one might want to avoid building a shared library.
Locally (not installation-global) I have been playing with this in two places:
- when creating GoogleTest based executables, where - at least for a long time - it was suggested to link the GoogleTest code statically.
- when creating a (shared) library for a Device Support that should contain its low level driver library, i.e., link it statically.
Cheers,
~Ralph