[Qt-interest] LGPL and static linking

[william.crocker at analog.com]

> On Tuesday 01 December 2009 14:25:43 william.crocker at analog.com wrote:
>   
>> Konrad Rosenbaum wrote:
>>     
>>> On Tuesday 01 December 2009 13:57:32 Robin Helgelin wrote:
>>>       
>>>> What about Webkit? I was told that as Webkit is LGPL, I'm not able to
>>>> static link to Webkit even though I have a commercial license of Qt.
>>>> If this also happens with QtScript, it means that all licenses becomes
>>>> unusable for us if we still want to use the whole Qt stack.
>>>>         
>>> out of curiosity: why do people prefer static linking? Why do you
>>> consider dynamic linking bad?
>>>       
>> My application runs as root and so use of LD_LIBRARY_PATH (etc) is not
>> permitted
>> and I do not want to have to worry about how every computer among the
>> thousands on which it runs within my enterprise finds the Qt libs.
>>     
>
> So why not link dynamically and let the system use the system-wide installed 
> Qt library? No need for LD_LIBRARY_PATH if /usr/lib (or any other lib-path in 
> /etc/ld.so.conf) contains the libraries...
>
>
>   

My enterprise covers the globe and between the USA and China (for example)
there is no system wide Qt library. Perhaps there could, but I still 
would not
want to worry about it or count on it. I like to build my app, test my 
app and then
distribute knowing that the user will run what I intended.

Bill