Update Readme

[SCordibella]

Dear community, I am not an openWRT expert, but I think that the Readme of this repository is a bit trivial.
Is this Qt porting officially supported in openWRT? If yes I think that calling it just "video" is not enough...
Can someone update describing that there is a Qt version for openWRT here?

Regards,
Stefano.

[mirko]

Qt is /one/ set of packages in this feed and while for a long time it was kinda the only one, just recently there was support committed for wayland.
It's supposed to be the home of packages mainly used on devices with displays.
It's not not clear to me what you'd like the README to state explicitly, but feel free to create an PR.

[SCordibella]

Thank you @mirko for your answer. I try to explain better my scenario.
I use Qt to build a middleware without the graphic part, it run on a headless gateway.
Now I am evaluating to move on a lower target hardware and openWRT seems to be an optimal solution since it is supported on a grater number of devices.
I supposed that this repository (or feed) was intended to store the Qt framework, but as you tell me this contains a more general graphics packages.
I don't want to change the meaning of this feed, for now I can import all the packages and then select just the Qt part that I need to use.
Generally speaking, since Qt is not only adopted for the graphics (ie: serial port, db connection, network layer, BLE, ...), are there any plan to move Qt component on a separate feed?

[mirko]

I don't see the benefit of having Qt in its own feed - please elaborate on that.
As you say, Qt can be used without GUI, but then - where to draw the line?
Is lcd4linux also video/graphics related, despite it just accessing the serial port? Xorg, which can also be used just as xserver without displays being connected?
The main reason for Qt (and all the package in this video feed) not being in the official packages feed[1] is, that if we (OpenWrt) make a full build with all packages being selected, that we can just exclude the video feed. It's too much of a niche for the time being. And requires a lot of space and resources to build on our build servers.
However there's discussion going on whether to move Qt into the official packages feed[1].
Either way, there's no plan of having Qt in its very own feed and I don't see in which way something or somebody would benefit from it(?)

[1]https://github.com/openwrt/packages/

[SCordibella]

I guess that this video feed was created sometimes ago and IMHO the misunderstanding is related to the fact that Qt at that time was intended mainly as a graphical library. Nowadays Qt can cover many other aspects and the main benefit to have it in its own feed is to better spread the information about the Qt support in openWRT.
Googling around it was not clear to me if the Qt framework was supported or not in openWRT, my suggestion to better clarify this point is to handle Qt framework in a proper feed (I don't know if in official feeds or not).
I am not an openWRT expert and I don't know the implication of including Qt in the standard packages, however from my understanding in a build system libraries are supported without a specific relationship with other components. Again the actual situation of the Qt package could be related to the initial intended use (only video/graphical library) or maybe it is not clear to me how the openWRT feeds works.

[Neustradamus]

What is the status of this ticket?

There is always this PR:

• qt5base: Update to 5.15.2, add debian patches #23