> Looks like you're somehow mixing a host Qt and a cross-compiled Qt? lupdate assumes that lupdate-pro is located in the same host Qt that lupdate belongs to. That's why LibraryExecutables is used.
Yocto sdk generates Qt tools to be used on the host machine, but the paths are not relative to the sdk in the qt.conf. I believe these should be relative to the sdk. Otherwise the host tools in the sdk can't be used > Why is there a separate qt.conf? Separate qt.conf are created by the populate_sdk_qt6_base.bbclass: https://code.qt.io/cgit/yocto/meta-qt6.git/tree/classes/populate_sdk_qt6_base.bbclass#n45 ________________________________ From: Jörg Bornemann <joerg.bornem...@qt.io> Sent: Friday, June 2, 2023 1:13 PM To: Ahmad, Arslan (DI SW CAS ES LI MEL) <arslan.ah...@siemens.com>; development@qt-project.org <development@qt-project.org> Subject: Re: [Development] unable to use lupdate(qt tools) in yocto sdk due to incorrect paths On 5/30/23 16:50, arslan.ahmad--- via Development wrote: > When running lupdate from a yocto sdk, I get the following error: > > $ lupdate -pro example.pro > sh: 1: /usr/libexec/lupdate-pro: not found Looks like you're somehow mixing a host Qt and a cross-compiled Qt? lupdate assumes that lupdate-pro is located in the same host Qt that lupdate belongs to. That's why LibraryExecutables is used. > The same problem occurs again when it enters usr/libexec since there is a separate qt.conf Why is there a separate qt.conf? -- Jörg Bornemann | The Qt Company
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
