Introducing the Qt Lite project – Qt for any platform, any thing, any size
1–10 of 38 posts
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#2"At least for now, the configuration tooling will be a part of the Qt for Device Creation product, and not open source."
I do wonder how a lot of companies's dual license model is going to interact with the IoT / embedded world.
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#3The amount of editorial in this post is mind blowing. Am I the only one who found it extremely hard (yes, extremely) to sift through all the blurb of text. In the end, I am not even sure what is being released.
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#4The new configuration system in Qt, allows your define the content you need from each module in much more detail for your project and easily allows for feature based tailoring of the Qt modules. We are starting with enabling this fully for Qt Core, Qt Network, Qt GUI, Qt QML and Qt Quick. You can now fine tune which features from these modules you want to include in your project. There is no longer any need to include unnecessary features.
To be clear, this potentially reduces binary sizes, but it does not by itself change run-time performance.
No Open GL Requirement ... The Qt Quick 2D renderer can work in software only, but it is also designed to utilize accelerated 2D operations, for devices that packs a little bit more punch, but still doesn’t have full OpenGL support.
I wonder what kinds of devices this is intended for? Presumably, they are a very important market for Qt to have implemented this? And these devices have graphics displays but they lack GPUs? What device could that be?
CPU software rendering seems like a step backwards for performance. GPUs and OpenGL must be more energy efficient at this task than software rendering, and I would imagine that important embedded devices with graphics displays must all have GPUs or will in the future?
I would have thought that "Qt for any platform" would include web browser (WebAssembly / Emscripten / WebGL) but no such luck. Based on the title, I thought this was going to be some drastic optimization of Qt's GUI. It doesn't sound like that's the case.
I haven't used Qt on embedded devices, but I've looked at several demos of Qt compiled to JavaScript with Emscripten [1] and the results seem very slow. Part of the reason seems to be that these Emscripten demos have Qt falling back to software rendering, instead of using WebGL accelerated rendering ... I don't think that another software rendering backend for Qt solves this problem.
[1] http://vps2.etotheipiplusone.com:30176/redmine/projects/emsc...
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#5The amount of editorial in this post is mind blowing. Am I the only one who found it extremely hard (yes, extremely) to sift through all the blurb of text. In the end, I am not even sure what is being released.
[deleted]
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#6The new configuration system in Qt, allows your define the content you need from each module in much more detail for your project and easily allows for feature based tailoring of the Qt modules. We are starting with enabling this fully for Qt Core, Qt Network, Qt GUI, Qt QML and Qt Quick. You can now fine tune which features from these modules you want to include in your project. There is no longer any need to includ…
Automotive In-Vehicle-Infotainment (IVI) systems that feature embedded SoCs running Linux for the GUI on an MPU and embedded RTOSs on MCUs for some of the more real-time/routine functions. Energy efficiency is secondary to the unnecessary cost/performance profile of building in a GPU to render relatively simple dashboard graphics.
The automotive market is the fastest-growing (and one of the largest) vertical markets for embedded MCU/MPUs, and by extension, embedded software.
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#7The amount of editorial in this post is mind blowing. Am I the only one who found it extremely hard (yes, extremely) to sift through all the blurb of text. In the end, I am not even sure what is being released.
I'm impressed you even managed to start reading. I only scrolled...
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#8The new configuration system in Qt, allows your define the content you need from each module in much more detail for your project and easily allows for feature based tailoring of the Qt modules. We are starting with enabling this fully for Qt Core, Qt Network, Qt GUI, Qt QML and Qt Quick. You can now fine tune which features from these modules you want to include in your project. There is no longer any need to includ…
Automotive In-Vehicle-Infotainment (IVI) systems that feature embedded SoCs running Linux for the GUI on an MPU and embedded RTOSs on MCUs for some of the more real-time/routine functions. Energy efficiency is secondary to the unnecessary cost/performance profile of building in a GPU to render relatively simple dashboard graphics. The automotive market is the fastest-growing (and one of the largest) vertical markets…
It's not my area, but I have a hard time believing that any competitive, modern IVI would be missing GPU integration. Just looking briefly, both Qualcomm [1] and NVIDIA [2] automotive systems have on-board GPUs.
[1] https://www.qualcomm.com/products/automotive/infotainment [2] http://www.nvidia.ca/object/drive-cx.html
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#9Earlier quoted context omitted.
Automotive In-Vehicle-Infotainment (IVI) systems that feature embedded SoCs running Linux for the GUI on an MPU and embedded RTOSs on MCUs for some of the more real-time/routine functions. Energy efficiency is secondary to the unnecessary cost/performance profile of building in a GPU to render relatively simple dashboard graphics. The automotive market is the fastest-growing (and one of the largest) vertical markets…
It's not my area, but I have a hard time believing that any competitive, modern IVI would be missing GPU integration. Just looking briefly, both Qualcomm [1] and NVIDIA [2] automotive systems have on-board GPUs. [1] https://www.qualcomm.com/products/automotive/infotainment [2] http://www.nvidia.ca/object/drive-cx.html
Check out Freescale and Renesas solutions. They are major automotive SoC players. The Renesas R-Car platform does integrate a dual-core Power-VR GPU:
https://cache.freescale.com/files/32bit/doc/fact_sheet/IMX6S...
https://www.renesas.com/en-us/solutions/automotive/products/...
Re: Introducing the Qt Lite project – Qt for any platform, any thing, any size
#10Earlier quoted context omitted.
Automotive In-Vehicle-Infotainment (IVI) systems that feature embedded SoCs running Linux for the GUI on an MPU and embedded RTOSs on MCUs for some of the more real-time/routine functions. Energy efficiency is secondary to the unnecessary cost/performance profile of building in a GPU to render relatively simple dashboard graphics. The automotive market is the fastest-growing (and one of the largest) vertical markets…
It's not my area, but I have a hard time believing that any competitive, modern IVI would be missing GPU integration. Just looking briefly, both Qualcomm [1] and NVIDIA [2] automotive systems have on-board GPUs. [1] https://www.qualcomm.com/products/automotive/infotainment [2] http://www.nvidia.ca/object/drive-cx.html
And the price difference between a device that didn't have gpu compared to those that don't will just shrink over time so any margin you might get yesterday will not be what you can get in the future.