Hacker News new | ask | show | jobs
by fc417fc802 106 days ago
Right but it's a perfectly functional (even remarkably feature complete) UI toolkit without the copyleft addons.

> You also need a commercial license for automotive and embedded deployments.

How does that work? The LGPL (really any OSI license) isn't compatible with additional usage restrictions.
2 comments
heavyset_go 105 days ago
You generally can't adhere to the LGPL in automotive or embedded deployments: the user can't link their own Qt libs in their auto/embedded device.

Slint has a similar license

link
jenadine 105 days ago
> You generally can't adhere to the LGPL in automotive

"Can't" or "won't"? The UI process is not usually the part that need certification.

> Slint has a similar license

Indeed, but Slint's open source license is the GPL and not the LGPL. And its more permissive license is made for desktop apps and explicitly forbid embedded (so automotive)

link
LtWorf 105 days ago
I'm guessing some parts of code are needed to make it run on those platforms and aren't LGPL.
link