> Qt Design Studio is available today as a free tool for everyone to try out and evaluate. You will need a commercial Qt developer license to distribute your UIs created with Qt Design Studio.
> We are also working on an open source version with a limited feature set, to be published in December.
The Qt library itself has both commercial and LGPL licenses. You can safely use LGPL libraries in commercial products with a couple obscure provisions: it's commonly held the library has to be dynamically linked, the user has the right to replace the Qt dynamic libraries, and maybe a few other inconsequential things.
I know one major vehicle manufacturer that won't go past 5.6 because of this reason. They put it right in the RFP.
I'd think a major vehicle manufacturer should be able to pay for the commercial license?
For them FOSS is a way to cut down development costs, while not contributing anything back, not even bug reports.
The legal and warranty issues around letting customers reflash their dashboards are what the company wants to avoid.
Therefore, they are deliberately chosing to use the FOSS version to avoid to pay the commercial one while keeping their hardware as closed as can be.
"Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source."
So not exactly the toolchain, but definitely allows reinstallation of upgraded libraries. I didn't know.
But there is a "problem" using Qt to release proprietary software, of course, because Qt is free, and perhaps parent isn't aware of the distinction between commercial and proprietary?
(That said, whenever possible please give back to the FSF community)
This is of course complicated by SaaS and all that is covered in more detail in Affero license and in that field I'm out of my depth.
Oh also, I am not a lawyer, if you're developing something commercially or otherwise reading this for advice please take a moment to consult a professional.
> Oh also, I am not a lawyer, if you're developing something commercially or otherwise reading this for advice please take a moment to consult a professional.
Absolutely!