Re: [PATCH 00/15] Add libunistring-optional module

[Pádraig Brady]

On 10/04/10 19:43, Paolo Bonzini wrote:
> On 04/10/2010 05:43 PM, Pádraig Brady wrote:
>> Thanks Paolo.
>> That's a nice feature to have.
>> I.E. statically link the lib when not present on the system.
>> It would be useful when one wanted to build a standalone sed
>> for example on older or non linux systems, with the caveat
>> that the binary would be a fair bit larger.
>> I don't think we'll use this in coreutils for example
>> due to the extra memory each util would use.
> 
> You mean you'd keep libunistring static or shared?  If the latter, I
> agree that most coreutils should not need libunistring, but (after
> double checking this) IGNORE_UNUSED_LIBRARIES_CFLAGS should handle it.
> For the few that require it, libunistring would be shared between all
> programs using it so memory is not a very important issue.

I had assumed that only the utils needing a built-in libunistring
would actually link it in, but thanks for confirming that.
I still was only considering a shared lib as there are now 100
coreutils and at least 10 would need libunistring.
Though in saying that some platforms only include GNU sort for example,
so providing this as an option might be useful.

thanks again,
Pádraig.