<div dir="ltr"><div><div><div><div><div><div>In addition to Marcus's comments I would liker to add that <br><br>even under LGPL you could build QT statically ( you would have to agree to provide obj files on request though ).<br>
</div><div>I am pretty sure google may provide you more information.<br><br></div>In practice this is pointless and people normally would not ask for it, but somebody can,<br></div><div>so you would have to be ready to do it.<br>
</div><div><br></div>As for mixing static and dynamic libraries you have to make sure that all of them use the same C runtime libraries.<br></div>You can build static library using dynamic CRTs and opposite.<br><br></div>
Mixing different type of CRTs usually result in exceptions and undefined behavior.<br><br></div>Regards,<br></div> Alex<br><div><div><div><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div>
</div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Aug 17, 2013 at 8:40 AM, Marcus D. Hanwell <span dir="ltr"><<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sat, Aug 17, 2013 at 11:22 AM, John Anaia <<a href="mailto:john.anaia@gmail.com">john.anaia@gmail.com</a>> wrote:<br>
> Dear vtkusers,<br>
><br>
> I am using LGPL Qt with VTK on Windows and I know that I should use dynamic<br>
> Qt build (DLLs) though there are exceptions. In the case of dynamic Qt<br>
> build, may I use a static VTK build to reduce the number and size of my<br>
> distribution files? BTW, what type of build should I choose for my<br>
> application, static or dynamic? Any specific concerns and considerations for<br>
> any of static and dynamic build combinations?<br>
><br>
</div></div>You are entirely constrained by the LGPL license, and that is in Qt.<br>
Any libraries/executables that statically link to Qt would be covered<br>
by the conditions placed upon it by the LGPL (including any of the VTK<br>
Qt integration libraries. VTK is BSD licensed, and you can statically<br>
link to it without any concerns over copyleft licensing clauses. I am<br>
not a lawyer, and to be certain you need someone who knows software<br>
licensing well to examine your particular situation, but you must<br>
ensure that all LGPL components are dynamically linked in order for<br>
your application to remain free of any GPL licensing requirements.<br>
<br>
You can always buy a commercial Qt license too, and then be free to<br>
statically link Qt too. Your questions are best directed to a Qt list<br>
as it is their license that most tightly constrains your options.<br>
<br>
Marcus<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the VTK FAQ at: <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
</blockquote></div><br></div>