Bug#637758: Distributing static libraries

Reinhard Tartler siretart at tauware.de
Mon Aug 15 09:59:01 UTC 2011


On Mon, Aug 15, 2011 at 10:11:33 (CEST), Fabian Greffrath wrote:

> Am 15.08.2011 09:42, schrieb Reinhard Tartler:
>> On Mon, Aug 15, 2011 at 08:55:47 (CEST), Fabian Greffrath wrote:
>>
>>> Am 15.08.2011 03:48, schrieb Andres Mejia:
>>>> We could make these users build the libraries themselves, but then
>>>> they would also need to build all the build dependencies as well for
>>>> the library they need. This can be quite a burden on various
>>>
>>> He? Why would I have to recompile a library's build-dependencies in
>>> order to create a static library from it?
>>
>> Because in order to link an application statically, each and every
>> dependent (static) library needs to be available as well.
>
> Sure, but that's not required to *build* a static library and
> furthermore not an issue that we can address in our library packages.

Well, it depends if you expect the libraries to be of any practical use.

I could imagien as valid use caseto produce a (partly) statically built
binary that works on a larger amount of distributions. But granted, we
are now in the speculation area.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4



More information about the pkg-multimedia-maintainers mailing list