[tylerag]

I dunno, that isn't terrible.

The terrible part is where if you pay for a commercial license to use it in a proprietary application, you can't stand within 50 feet of the LGPL version.

https://www.qt.io/terms-conditions/:

“Prohibited Combination” shall mean any effort to use, combine, incorporate, link or integrate Licensed Software with any software created with or incorporating Open Source Qt, or use Licensed Software for creation of any such software.

So you can't use KDE to write a program that links against the proprietary QT libraries.

[lmm]

> So you can't use KDE to write a program that links against the proprietary QT libraries.

The way I read it that's fine, it's the other way around that's forbidden - you're not allowed to use the commercial-licensed version to work on KDE.

[fluoridation]

I think what it's saying is that you can't use licensed Qt to create software that uses both it and OSS Qt, not that you can't use software that uses OSS Qt to create software that uses licensed Qt.

[jonhohle]

Is it ABI compatible? You could run KDE with the proprietary libraries.

[jenadine]

That would be violating the proprietary licence terms

[ktm5j]

Forgive me if I'm missing something obvious, but could you explain why that is?

[tylerag]

KDE was created with open source Qt. As in, the developers that wrote KDE used the LGPL version of Qt.

To repeat myself, “Prohibited Combination” shall mean any effort to use, combine, incorporate, link or integrate Licensed Software with any software created with or incorporating Open Source Qt.

[ktm5j]

Oh goodness, I'm so sorry you had to repeat yourself.. The reason I started my question by saying "forgive me if I'm missing something obvious" is because I'm no expert on licensing issues and was asking a genuine question.