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

[Jérôme Godbout]

Hi,
We are not going into the Qt MCU code based, we will have a full fledge Linux build with Yocto and plan on using a full Qt with Qml views. Open Source is not possible without releasing the cie application business layer which the client does not want to do for obvious reason.

Let’s make the question clear:
Can the commercial Application be used with a Yocto build into a custom arm device?

[signature_106982083]<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: Tuukka Turunen <tuukka.turunen at qt.io>
Date: Thursday, December 14, 2023 at 9:59 AM
To: Jérôme Godbout <jgodbout at dimonoff.com>, Qt Interest <interest at qt-project.org>
Subject: Re: Yocto is application or device creation license???
Hi,

The meta-qt6 layer is available at: https://code.qt.io/cgit/yocto/meta-qt6.git/tree/ It works for both commercial as well as open-source Qt as described at: https://code.qt.io/cgit/yocto/meta-qt6.git/tree/README.md

Your email mentions MCU, so in case you are looking to use Qt for MCUs it is a separate codebase, which is not dual licensed. More info: https://www.qt.io/product/develop-software-microcontrollers-mcu

The commercial Qt for Device Creation subscription includes prebuild binaries, convenience items, as well as some additional functionality. You can check what is available under which license bundle via: https://www.qt.io/product/features

We recommend using the commercial Qt for Device Creation product when making embedded devices. It is also possible to build embedded devices using the open-source license option as long as you ensure to meet the requirements set by open-source licensing. You can check more information on the L/GPL requirements at: https://www.qt.io/licensing/open-source-lgpl-obligations

Yours,

                                Tuukka


From: Interest <interest-bounces at qt-project.org> on behalf of Jérôme Godbout via Interest <interest at qt-project.org>
Date: Thursday, December 14, 2023 at 16:36
To: Qt Interest <interest at qt-project.org>
Subject: [Interest] Yocto is application or device creation license???
Hi,

I have a client who is looking for a GUI stack for their SPA devices. The device use a yocto we build for them. The Fuzzy license of Qt is not very clear on where does Yocto build fall in term of licensing.

My understanding if fall into the Linux embedded and force them to go into the device license I think. But this will be a show stopper for them if they have to paid royalty fee. Does Yocto Linux count as Linux Desktop, since we are building a desktop on arm chipset in the end.

The device creation is just plain impossible, the royalty fee is above the cost of the MCU itself, which is a no go.

I feel like I always end up in that impossible licensing problems with Qt, the embedded license is out of touch aside from huge expensive system like car!

So far, we look at Qt for hospital bed, SPA, car charging units… The price is just a show stopper at each time…


[signature_917022966]<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/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231214/8f084280/attachment-0001.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/20231214/8f084280/attachment-0008.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/20231214/8f084280/attachment-0009.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/20231214/8f084280/attachment-0010.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/20231214/8f084280/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 6212 bytes
Desc: image005.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231214/8f084280/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 497 bytes
Desc: image006.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231214/8f084280/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 660 bytes
Desc: image007.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231214/8f084280/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 21532 bytes
Desc: image008.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20231214/8f084280/attachment-0015.png>