[vtkusers] VTK + Qt static or dynamic build

[Alex Malyushytskyy]

In addition to Marcus's comments I would liker to add that

even under LGPL you could build QT statically ( you would have to agree to
provide obj files on request though ).
I am pretty sure google may provide you more information.

In practice this is pointless and people normally would not ask for it, but
somebody can,
so you would have to be ready to do it.

As for mixing static and dynamic libraries you have to make sure that all
of them use the same C runtime libraries.
You can build static library using dynamic CRTs and opposite.

Mixing different type of CRTs usually result in exceptions and undefined
behavior.

Regards,
   Alex



On Sat, Aug 17, 2013 at 8:40 AM, Marcus D. Hanwell <
marcus.hanwell at kitware.com> wrote:

> On Sat, Aug 17, 2013 at 11:22 AM, John Anaia <john.anaia at gmail.com> wrote:
> > Dear vtkusers,
> >
> > I am using LGPL Qt with VTK on Windows and I know that I should use
> dynamic
> > Qt build (DLLs) though there are exceptions. In the case of dynamic Qt
> > build, may I use a static VTK build to reduce the number and size of my
> > distribution files? BTW, what type of build should I choose for my
> > application, static or dynamic? Any specific concerns and considerations
> for
> > any of static and dynamic build combinations?
> >
> You are entirely constrained by the LGPL license, and that is in Qt.
> Any libraries/executables that statically link to Qt would be covered
> by the conditions placed upon it by the LGPL (including any of the VTK
> Qt integration libraries. VTK is BSD licensed, and you can statically
> link to it without any concerns over copyleft licensing clauses. I am
> not a lawyer, and to be certain you need someone who knows software
> licensing well to examine your particular situation, but you must
> ensure that all LGPL components are dynamically linked in order for
> your application to remain free of any GPL licensing requirements.
>
> You can always buy a commercial Qt license too, and then be free to
> statically link Qt too. Your questions are best directed to a Qt list
> as it is their license that most tightly constrains your options.
>
> Marcus
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20130819/d9a0f2f6/attachment.htm>