3 ms·

You'll need a license if it's not open source as far as I can tell... I would love to use Qt but their licensing and terms just immediately kill it for me: htt

You'll need a license if it's not open source as far as I can tell... I would love to use Qt but their licensing and terms just immediately kill it for me: https://www1.qt.io/faq/#_Toc_2_5 https://www1.qt.io/faq/#_Toc_2_5

CamperBob2 9y ago
It's LGPL-compatible, though, isn't it? Can't you just wall off the Qt layer in a separate library, and release the source to that?
- freedomben 9y ago
  IANA lawyer, but my understanding is that you are correct. The LGPL doesn't force you to release the entire source, unless you are shipping a single static binary. If you dynamically link, you are good to go.
- movedx 9y ago
  Perfect for me: develop the front end using Qt (on an OSS licence) and Go, which is just a dumb data rendering layer with caching, and keep all the actual business logic server-side. I'll happily open-source a "shell" :)
mkl 9y ago
I think you misread that. For any use, you need a licence, and the possible licences to choose from are 1. Commercial, or 2. Open source (GPL or LGPL). You can make commercial software using one if the open source licenses. (Of course; otherwise it wouldn't be an open source licence.)