4 ms·
Just yesterday I was reviewing Qt, GTK and Electron as possible choices for some GUI exercise, and _at a glance_ Qt sure looks likely to involve committing to G
by the_local_host 6y ago
Just yesterday I was reviewing Qt, GTK and Electron as possible choices for some GUI exercise, and _at a glance_ Qt sure looks likely to involve committing to GPL, which is a pretty irreversible commitment to have to make at the outset of a project.
I guess it's possible to sort through the individual components and find a subset that is LGPL and not GPL, but that's a lot of work, especially if you're not familiar with Qt already and need to make a decision.
- brnt 6y agoIf you link properly, GPL isnt a problem: https://news.ycombinator.com/item?id=23321448 https://news.ycombinator.com/item?id=23321448
- Rochus 6y agoYou seem to mix that up with LGPL. With GPL the linked app also becomes GPL. With LGPL this is not the case; usually apps link to Qt dynamic libraries which is ok.
- h_anna_h 6y agoThis is about LGPL
- detaro 6y agoCorrect, although LPGL is the primarily relevant one for Qt. Only a few relatively niche parts of it are under GPL.
- the_local_host 6y agoI guess that would work, the time and effort involved in getting end-users to link the application makes downloading a large Electron binary seem downright pleasant.
- ubercow13 6y agoYou can just ship your application with a dynamically linked Qt library file(s). There is no extra step for the user.