https://www.qt.io/blog/qt-offering-changes-2020I took this recap from
https://valdyas.org/fading/software/about-qt-offering-changes-2020:
- Long Term Support releases remain commercial only (the post doesn’t mention this, but those releases also need to be released under a free software license within a year to adhere to the agreement, at least to my understanding).
- Access to pre-built binaries will be restricted: put behind an account wall or be only available to commercial license holders
- And there’s a new, cheaper license for small companies that they can use to develop, but not deploy their work to customers.
Unrelated:As my own experiment I copied cbindings from the qt5 inferface of Lazarus (2.0.6) and tried to port it to CopperSpice. Check CopperSpice here:
https://www.copperspice.com/But I can't get any further. Because even building the binding
with Qt5 itself with Qt 5.11 from my Debian 10 system failed. QtCreator said there is no x11extras nor QX11Info. I don't know how you guys managed to got it build in the first place.
This mean the binding is lacked of maintenance. Could this Qt offering changes give us an opportunity to revisit it all?
Disclaimer:I searched the internet for Qt fork and found CopperSpice. I'm
not related with them. I
don't hype for them.
The fact is I like CopperSpice because it has Qt MOC removed. But I also dislike their build system, CMake. I tried to port the Qt5Pas.pro to CMake but finally gave up. CMake just is not for me!
p/s: if I could get further, I still can't become the maintainer of this, potentially, CopperSpice Widgetset for Lazarus. My computer is too old and slow to be able to smoothly build C++. Someone with a more powerful computer if interested could try if it even possible. I think to conversion from Qt5 to CopperSpice is not very painful, as I ran CopperSpice's PepperMill conversion tool on the binding's header successfully without any warnings.
p/s: sorry if you found my English to be clumsy, it's all Google translate with manual fixes by me.