First of all glad to hear you’re giving Torizon a try despite already having experience with Yocto.
Which is the way to do the kernel and u-boot cutomization? In Yocto we changed the sources and apply patches with recipes, with Torizon build tool is possible to do this? With the kernel I think that is not rocker science due to that we can add a dts custom file.
With u-boot how can I do that?
This is a bit complex but the general answer is “no”. But let me explain. As you noted device trees can be customized though this is a bit different than the kernel since device trees produce their own binary separate from the kernel binary. However if you actually want to modify the kernel sources itself and then compile a completely new kernel, that is not possible with TorzionCore Builder, same with U-Boot.
Now it wouldn’t be completely impossible to make the TorizonCore Builder tool do this. That said, we are not trying to re-invent the wheel with what Yocto already does. Yocto is already a powerful build system and in many cases it’s probably more “proper” to edit the kernel and such there then try to edit these outside of the build system.
Out of curiosity what kind of kernel/u-boot customizations are you trying to make?
For the documentation that I read the concept of TorizonOS is to run apps dockerized, is that correct?
Which is the correct way to add qt app in the docker image?
Correct. For adding apps to a docker image, well there’s a couple of ways you can do this. We do provide an IDE extension for Visual Studio Code that can help in this process: IDE Extension | Toradex Developer Center
If you want to tackle this more manually, the idea would be to add your application dependencies to a container image, build the application in the container image. Ship a container image with your application built in. If you want more kind of raw examples of how you would construct a container for an application you can look at our repository of samples here: GitHub - toradex/torizon-samples: All sample code related to TorizonCore project.
There are many samples here each with their own Dockerfile to build the container image for that containerized application.
Which version of qt libraries are installed in qt5-wayland-vivante docker image? I think that if doesnt give the version the latest version is installed, is that correct?
If you are using our container images, then we base our container images on Debian. For Torizon 6.X we’re using Debian bookworm. Therefore you can just check what the Debian package feeds provide for Debian bookworm, which looks like version 5.15.8: Debian -- Details of package qtbase5-dev in bookworm
For your opinion if we have really good Yocto skills is necesary to change with TorizonOS.
I would say it’s not “necessary” at all. Really this would be like asking should I boil water on the stove or with an electric kettle. Sure the process might differ here and there but in the end you get to the same end result. Obviously Torizon would have more appeal if one didn’t have any knowledge of Yocto whatsoever, though that is not the case for you. That said we have customers who like you are knowledgeable about Yocto, but still use Torizon OS. It’s more of a preference than anything I would say.
Now just to turn the question back on you. For what reason are you and your team considering Torizon if you are already good with Yocto?