[Interest] Yocto is application or device creation license???

[Jérôme Godbout]

Hi,
If it may interest anybody, using Yocto is defacto embedded license required. So using Qt into your Yocto for a product make you enter into the royalty fee realm and an expensive one.

Another client that will use something else. It took the client 30 seconds to choose after the sale representative meeting. I cannot even think they gave such a price for over 50k unit per years…

It make 3 ridiculous pricing for embedded I get from Qt into the past years and a half for different clients. None when down that road, not because of the tech, but the embedded royalty are just plain out of this world for embedded devices. Maybe for a 20k$ car it can make sense, but when you make SPA equipment, hospital bed, power control box, it’s plain a no go for GUI. And we are not talking low volume client, 15k, 40k and the other was 75k-100k. Better, invest that money on bigger MCU/GPU, when the royalty is above the MCU price it’s plain insanity.

Sad, but I have not been able to use Qt in the past few years…

[signature_2639730570]<https://www.dimonoff.com/>
Jérôme Godbout, B.Eng.
Software / Firmware Team Lead
[Smart Phone avec un remplissage uni] (581) 777-0050
[Envelope avec un remplissage uni] jgodbout at dimonoff.com<mailto:jgodbout at dimonoff.com>
[World avec un remplissage uni] www.dimonoff.com<http://www.dimonoff.com>


From: Interest <interest-bounces at qt-project.org> on behalf of Thiago Macieira <thiago.macieira at intel.com>
Date: Thursday, December 14, 2023 at 4:00 PM
To: interest at qt-project.org <interest at qt-project.org>
Subject: Re: [Interest] Yocto is application or device creation license???
On Thursday, 14 December 2023 16:13:37 -03 Jérôme Godbout via Interest wrote:
> Can I use the Yocto Layers and Recipes in a build using BitBake (YP's build
> tool) to make a commercial application using the Application Development
> license?
>
> That’s my true question, is application development license allowed into
> that context or are we force to use the device creation license.

I think you or I are getting mixed on details.

Yocto Project, recipes, layers, and BitBake are just tools to accomplish the
build of your device. YP licences won't apply at the end. Only the cumulative
licence of all the software that you selected (by way of the layers) does and
the YP tools will create the BOM for you to analyse. This is where this
licence you're referring to comes into play.

So it doesn't matter how you built and deployed your Qt Commercial onto the
device, only that you did. Does that licence allow you to ship your device?
Does it require payment of per-unit royalties? Does it put extra requirements
on what you can or can't do? I can't answer that, since I don't know the
terms. You should get your legal department to make a decision. Qt Company's
opinion is an input, not a conclusion.

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231220/606324fc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6212 bytes
Desc: image001.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231220/606324fc/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 497 bytes
Desc: image002.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231220/606324fc/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 660 bytes
Desc: image003.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231220/606324fc/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 21532 bytes
Desc: image004.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231220/606324fc/attachment-0003.png>