[Development] The sorry state of the Qt6 cross compile experience

Dominik Holland dominik.holland at qt.io
Wed Feb 24 09:21:06 CET 2021

Am 24.02.21 um 08:47 schrieb Bogdan Vatra via Development:

> Hi,
>> You have some valid complaints, but:
>> BogDan Vatra via Development wrote:
>>> - the cross build installation is broken, instead to copy the tools from
>>> the QT_HOST_TOOLS folder,  it creates some scripts that has hardcoded
>>> paths to QT_HOST_TOOLS which runs the scripts from QT_HOST_TOOLS folder.
>>> Of course this makes the installation unusable on another computer. Even
>>> the "lib/cmake/Qt6/ qt.toolchain.cmake" contains hardcoded paths...
>> In distribution packaging, that is exactly what we want: in the packaged
>> cross Qt, use the known paths to our packaged host Qt instead of guessing
>> them at runtime (and often guessing wrong).
>    Most of the people out there are using yocto, buildroot to create a nice
> SDKs with all the things they need  which will share with their collages, of
> course having hardcoded paths will break these SDKs. Not even with conan will
> not work for the same reason... Only a fraction (I'm one of them) will use
> debian for linux cross compiling. For Android cross compiling I believe that
> almost nobody is using distribution Qt packages...
If you are using yocto, then you can build Qt in yocto as well. Which 
means yocto also creates the host Qt for you in the SDK with the correct 
pathes (according to their environment file).

More information about the Development mailing list