On Friday, 2 June 2023 05:18:57 PDT Ivan Solovev via Development wrote:
> I'd like to request a Feature Freeze exception for the C++20 comparison
> task, due to the last-minute discussions about the names of the helper
> functions to be used. This is important because these helper functions are
> i
El martes, 16 de mayo de 2023 16:12:36 -03 Thiago Macieira escribió:
> On Monday, 15 May 2023 21:23:21 PDT Thiago Macieira wrote:
> > We still don't know why this happened because all our attempts
> > to find out why cause the problem to disappear.
>
> BTW, we found that the user's application was
Hi,
I'd like to request a Feature Freeze exception for the C++20 comparison task,
due to the last-minute discussions about the names of the helper functions to
be used. This is important because these helper functions are intended to be
exposed as public API.
The task is https://bugreports.qt.
Hi all,
Just a reminder: Qt 6.6 Feature Freeze will be in effect today. As earlier you
can continue staging ready changes (== ones having +2 today) during the weekend
as well. But if new feature isn't ready today you need to get the exception to
get it in Qt 6.6.
The target is to branch from '
> Changing Prefix to be a relative path would then break all qmake builds.
do you see any possible workaround for this?
From: Development on behalf of Samuli
Piippo via Development
Sent: Friday, June 2, 2023 2:15 PM
To: development@qt-project.org
Subject: Re:
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 would
> 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
Congratulations to Jere. Approver rights have been granted.
--
Alex
From: Development on behalf of Tomi
Korpipää via Development
Sent: Friday, 12 May 2023 09:12
To: development@qt-project.org
Subject: [Development] Nominating Jere Tuliniemi for approve
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