On 6/3/23 23:19, Lisandro Damián Nicanor Pérez Meyer wrote:
Changing Prefix to be a relative path would then break all qmake builds.
do you see any possible workaround for this?
Switching to CMake should do the trick I guess.
Alternatively,
- rename qt.conf to somethingelse.conf
- rename
Hi,
On Fri, 2 Jun 2023 at 06:24, arslan.ahmad--- via Development
wrote:
>
> > Changing Prefix to be a relative path would then break all qmake builds.
>
> do you see any possible workaround for this?
Switching to CMake should do the trick I guess.
--
Development mailing list
Development@qt-pro
Re: [Development] unable to use lupdate(qt tools) in yocto sdk due to
incorrect paths
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 qm
/meta-qt6.git/tree/classes/populate_sdk_qt6_base.bbclass#n45
From: Jörg Bornemann
Sent: Friday, June 2, 2023 1:13 PM
To: Ahmad, Arslan (DI SW CAS ES LI MEL) ;
development@qt-project.org
Subject: Re: [Development] unable to use lupdate(qt tools) in yocto sdk due to
incorre
-qt6.git/tree/classes/populate_sdk_qt6_base.bbclass#n45
From: Jörg Bornemann
Sent: Friday, June 2, 2023 1:13 PM
To: Ahmad, Arslan (DI SW CAS ES LI MEL) ;
development@qt-project.org
Subject: Re: [Development] unable to use lupdate(qt tools) in yocto sdk due to
incorrect pa
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 lupd
When running lupdate from a yocto sdk, I get the following error:
$ lupdate -pro example.pro
sh: 1: /usr/libexec/lupdate-pro: not found
qt.conf:
[Paths]
Prefix = /usr
Headers = /usr/include
Libraries = /usr/lib64
ArchData = /usr/lib64
Data = /usr/share
Binaries = /usr/bin
LibraryExecutables = /usr
