On Sunday, 24 November 2019 09:25:37 PST Olivier Goffart wrote:
> So moc stays much faster than actually compiling, but it has been reported
> that moc does not play nice with ccache or distributed compile farm.
There's no reason why moc can't be ccache'd.
As for a compile farm, the big problem
On 24.11.19 12:24, Giuseppe D'Angelo via Development wrote:
Il 21/11/19 17:38, Joerg Bornemann ha scritto:
It works and produces seemingly the correct output, able to consume
modern C++ constructs.
But it's sloow. Running on Qt Creator takes 1 min with the old
parser, and 50 min with the
Il 21/11/19 17:38, Joerg Bornemann ha scritto:
It works and produces seemingly the correct output, able to consume
modern C++ constructs.
But it's sloow. Running on Qt Creator takes 1 min with the old
parser, and 50 min with the new one.
Related question: does also a clang-based moc suffer
Am 22.11.19 um 21:25 schrieb Kai Pastor, DG0YT:
Am 22.11.19 um 17:03 schrieb Kai Köhne:
Keep in mind that you need this context available both at runtime and
at lupdate time. That is, the only setup how this IMO would reliably work
is if we make the context a part of the tr() call -
On Fri, Nov 22, 2019 at 12:25:21PM +, Joerg Bornemann wrote:
On the topic of switching to gettext:
My searches yielded nothing.
because our archives are incomplete and badly indexed, and clearly
nobody bothered to make a jira task (at least a publicly visible one).
It would be cool to
Am 22.11.19 um 17:03 schrieb Kai Köhne:
From: Development On Behalf Of
Joerg Bornemann
On 11/22/19 7:21 AM, Kai Pastor, DG0YT wrote:
Given the Qt Creator example, would it be feasible to make explicit
declaration of a file's context mandatory, at least for the existing
("fast") parser? If not
> -Original Message-
> From: Development On Behalf Of
> Joerg Bornemann
> Sent: Friday, November 22, 2019 1:25 PM
> To: Kai Pastor, DG0YT ; development@qt-project.org
> Subject: Re: [Development] QtCS2019 Notes: Clang-based cpp parser for
> lupdate
>
> On 1
On 11/22/19 7:21 AM, Kai Pastor, DG0YT wrote:
> Am 21.11.19 um 20:23 schrieb André Pönitz:
>> On Thu, Nov 21, 2019 at 07:48:41PM +0100, Oswald Buddenhagen wrote:
>>> a more radical and much simpler approach would be switching to gettext
>> The most prominent difference is the (usually) per-class
Am 21.11.19 um 20:23 schrieb André Pönitz:
On Thu, Nov 21, 2019 at 07:48:41PM +0100, Oswald Buddenhagen wrote:
a more radical and much simpler approach would be switching to gettext
The most prominent difference is the (usually) per-class automatic context
which I always found too clever to be
On Thu, Nov 21, 2019 at 07:48:41PM +0100, Oswald Buddenhagen wrote:
> On Thu, Nov 21, 2019 at 04:38:28PM +, Joerg Bornemann wrote:
> > There is the ongoing effort to replace the old outdated parser with a
> > clang, similar to what's been done in qdoc. The corresponding JIRA
> > issue is
On Thu, Nov 21, 2019 at 04:38:28PM +, Joerg Bornemann wrote:
There is the ongoing effort to replace the old outdated parser with a
clang, similar to what's been done in qdoc. The corresponding JIRA
issue is QTBUG-71835.
a more radical and much simpler approach would be switching to gettext
11 matches
Mail list logo
