News for hackers. Stuff that matters.

A comment on Qt Binding for Go with Support Desktop, Mobile and Embeddable. Parent comment

Re:Qt Binding for Go with Support Desktop, Mobile and Embedd... by htfy96 on Monday November 25, 2019 @05:50PM (#21633680)
One thing to notice is that the open-sourced version of Qt is under GPL/LGPL, which means if you statically linked it into the executable, your application is then infected by (L)GPL.
[ Parent | on HN ]
Re:Qt Binding for Go with Support Desktop, Mobile and Embedd... by kej on Monday November 25, 2019 @06:03PM (#21633824)
Your application is "infected" if you use Qt without a commercial license, regardless of how you link it. It's a little harder (but still possible) to comply with the LGPL requirements when you statically link, but you are bound to those requirements either way.
[ Parent | on HN ]
Re:Qt Binding for Go with Support Desktop, Mobile and Embedd... by groovebits on Tuesday November 26, 2019 @04:47AM (#21636839)
Pretty sure having it dynamically linked is ok with the open source licence
[ Parent | on HN ]
Re:Qt Binding for Go with Support Desktop, Mobile and Embedd... by kej on Tuesday November 26, 2019 @10:34AM (#21639133)
Right, my point is that static linking is also okay with the LGPL, albeit slightly more difficult in terms of what you have to make available to end users.
[ Parent | on HN ]
Re:Qt Binding for Go with Support Desktop, Mobile and Embedd... by therockhead on Tuesday November 26, 2019 @02:27AM (#21636266)
I believe the parent post is correct and mechanism used to link effects the licence.
[ Parent | on HN ]
Re:Qt Binding for Go with Support Desktop, Mobile and Embedd... by nickserv on Tuesday November 26, 2019 @03:08AM (#21636423)
If you want to ship closed source code based on other people's hard work, then you should pay. In this case by getting a Qt commercial license.
[ Parent | on HN ]