Using tags for the yocto builds is not going to help, since the way bitbake
tries to validate the SHA1s that are already being used in the meta-qt5 and
meta-qt6 recipes.
Instead, you can add
QT_MODULE_BRANCH_PARAM:append = ";nobranch=1"
somewhere in your own configs.
This tells bitbake to
, 12 January 2023 23:03:27 PST Samuli Piippo via Development wrote:
> Using tags for the yocto builds is not going to help, since the way bitbake
> tries to validate the SHA1s that are already being used in the meta-qt5 and
> meta-qt6 recipes.
That's an explanation that doesn't explain an
qt.conf is there mainly for qmake, which needs to know both target paths and
host paths. Now unfortunately, this also affects lupdate which expect
LibraryExecutables to be a host path, while qt.conf tells qmake that it's
really HostLibraryExecutables.
Changing Prefix to be a relative path
