Re: Should .a library contains non-reallocatable code?
Simon Richter writes ("Re: Should .a library contains non-reallocatable code?"):
> On 25.02.2015 15:35, Ian Jackson wrote:
> >> In libvxi-dev I provide a -fPIC .a library only, mainly for size reasons
> >> (the library consists of RPC proxy/stub code for the VXI-11 protocol,
> >> and is completely generated with rpcgen).
>
> > Do many other packages use that library ?
>
> No, just one.
>
> If that package were to be a shared library, the required space in the
> Packages file would be similar to the size of the files installed by the
> package. IMO, that's not really a good trade-off.
Ah, because of the requirement for the shared library to be in its own
package ? So you're actually just making a static-only library to
avoid metadata overhead. That's plausible, although I wouldn't
describe it as space reasons...
Ian.
Reply to: