Hi,
for this reason MITK only uses and *dynamically* links the LGPL part of Qt. The key is the dynamic linkage as the LGPL differentiates between static and dynamic linkage in contrast to GPL*. This way MITK is not "infected" with the LGPL license. As we bundle the Qt libraries in our installers, we have to and do follow the LGPL requirement of conveying the Qt source by offering it on our download server. BTW, MITK can be configured and built without Qt, for example, see the Minimal build configuration. Best, Stefan * In theory it is even possible to statically link to LPGL libraries as long as you provide your software in object format and clients are able to relink it (https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic?). ________________________________ Von: 이준영 <toz.l2...@gmail.com> Gesendet: Donnerstag, 8. Oktober 2020 08:54 An: mitk-users@lists.sourceforge.net Betreff: [mitk-users] Qt's license in MITK Workbench Hi, I just started using MITK, and I have some confusion about the Qt license within MITK. I know open source Qt's license is GPL or LGPL and MITK's license is BSD. AFAIK, if program 'A' depends on a module that is licensed under GPL or LGPL(if 'A' doesn't work without (L)GPL module), program 'A' must follow the module's (L)GPL license. The GUI of MITK Workbench seems to be based on Qt and I can't even generate a MITK project without installing Qt. I think this is a dependency on Qt, but, why can MITK be a BSD license? If I slightly modify the MITK project and distribute the ZIP file, which is the output file of the PACKAGE project build, MITK's Qt module is also included in the ZIP file. Can I still distribute under the BSD license with source code? Am I missing something or misunderstanding? Thanks for help.
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
