To bypass the MSVC limitation I think that you need to use array notation
instead of string literals, with the help of a tool such as xxd.
Apparently powershell has a command to more-or-less do it (format-hex),
with some PS magic it could maybe work without too much dependencies added
on windows...
On Friday, 31 May 2019 10:13:52 PDT Thiago Macieira wrote:
> rcc should be un-bootstrapped. The only use inside QtCore is for the MIME
> type database. We don't need a resource, though it compresses really well
> (roughly 10:1 with zstd). I'd simply make that a read-only sharable
> variable, which
On Friday, 31 May 2019 11:55:59 PDT Bogdan Vatra via Development wrote:
> > PCH is a nice to have, but does not stop us from building Qt.
> >
> > iOS support is a problem. We need to make sure the tools we choose support
> > us.
>
> Without PCH the build time will increase a lot.
20 to 50% at mo
În ziua de vineri, 31 mai 2019, la 19:03:46 EEST, Thiago Macieira a scris:
> On Thursday, 30 May 2019 22:45:02 PDT Bogdan Vatra via Development wrote:
> > Hi,
> >
> > În ziua de vineri, 31 mai 2019, la 08:36:31 EEST, Thiago Macieira a scris:
> > > On Thursday, 30 May 2019 15:51:26 PDT Konstantin T
31.05.2019, 12:37, "Tobias Hunger" :
> On Fri, 2019-05-31 at 01:37 +0300, Konstantin Tokarev wrote:
>> > I understand, but aside from qmake, I don't know of any build system that
>> > allows for building both host and target in the same build. That means
>> > whatever we use in Qt 6, we'll a s
On Friday, 31 May 2019 02:22:03 PDT Tobias Hunger wrote:
> Hi Thiago,
>
> On Thu, May 30, 2019 at 8:18 PM Thiago Macieira
>
> wrote:
> > On Wednesday, 29 May 2019 06:33:23 PDT Giuseppe D'Angelo via Development
> >
> > wrote:
> > > 2) should QRegExp stay in bootstrap? I have no idea of what's ha
On Thursday, 30 May 2019 22:45:02 PDT Bogdan Vatra via Development wrote:
> Hi,
>
> În ziua de vineri, 31 mai 2019, la 08:36:31 EEST, Thiago Macieira a scris:
> > On Thursday, 30 May 2019 15:51:26 PDT Konstantin Tokarev wrote:
> > > BTW, are you also planning to drop support for using PCH with GCC
Hey Guiseppe,
> On 31 May 2019, at 14:50, Giuseppe D'Angelo via Development
> wrote:
>
> Hi,
>
> It seems to me that many emails in the earlier deprecation thread were from
> users concerned by the problem of removal of functionality. This is not an
> old story.
>
> However, apart from the
Hi,
It seems to me that many emails in the earlier deprecation thread were
from users concerned by the problem of removal of functionality. This is
not an old story.
However, apart from the specifics of why deprecating a certain class /
what to replace it with / etc., there's a bigger thing
On 31/05/2019 11:06, Alberto Mardegan wrote:
I bet it's unused because everyone is using QList. But once we deprecate
QList, people will start asking for a CoW version of std::list.
QList has nothing to do with std::list!
(Except a very similar name.)
How many times does this need to be repeat
On Fri, 2019-05-31 at 01:37 +0300, Konstantin Tokarev wrote:
> > I understand, but aside from qmake, I don't know of any build system that
> > allows for building both host and target in the same build. That means
> > whatever we use in Qt 6, we'll a separate build for host tools when cross-
> > co
Hi Thiago,
On Thu, May 30, 2019 at 8:18 PM Thiago Macieira
wrote:
> On Wednesday, 29 May 2019 06:33:23 PDT Giuseppe D'Angelo via Development
> wrote:
> > 2) should QRegExp stay in bootstrap? I have no idea of what's happening
> > regarding to that in Qt 6.
>
> Bootstrap needs to go away in Qt 6.
On 30/05/19 18:34, Giuseppe D'Angelo via Development wrote:
> Hi,
>
> On 30/05/2019 10:23, Alberto Mardegan wrote:
>> I bet it's unused because everyone is using QList. But once we deprecate
>> QList, people will start asking for a CoW version of std::list.
>
> QList has nothing to do with std::l
13 matches
Mail list logo