> On 5 Jun 2019, at 00:39, Kevin Kofler wrote:
>
> Mutz, Marc via Development wrote:
>> I'd still like to deprecate them. QSDP is issuing atomic operations on
>> each mutable access hurting code-gen,
>
> Well yes, you have to use constData() or cast to const where needed. That
> does not reduc
On Monday, 3 June 2019 19:10:12 PDT Thiago Macieira wrote:
> First, I want to pass the XML source through
> xml sel -D -B -t -c /
>
> That will minify the source. That reduces the uncompressed size by about
> 10%.
>
> Second, I'm also thinking of compressing with gzip or zstd. The problem
On Tue, 04 Jun 2019 22:41:31 +0200
"Mutz, Marc via Development" wrote:
> That QThread is-a QObject has caused problems in the past. How to use
> QThread correctly has been the source of much discussion (e.g.
> https://blog.qt.io/blog/2010/06/17/youre-doing-it-wrong/), and any
> thread can have
On Tuesday, 4 June 2019 12:57:36 PDT Mutz, Marc via Development wrote:
> You talk about a particular incarnation of stdlibs, I was talking about
> the general case. Yes, in the case you describe, and _if_ libc++ is
> configured to be compatible (which in the past you have complained is
> not done c
On Tuesday, 4 June 2019 13:41:31 PDT Mutz, Marc via Development wrote:
> That QThread is-a QObject has caused problems in the past. How to use
> QThread correctly has been the source of much discussion (e.g.
> https://blog.qt.io/blog/2010/06/17/youre-doing-it-wrong/), and any
> thread can have an e
On Tuesday, 4 June 2019 10:07:46 PDT Lisandro Damián Nicanor Pérez Meyer
wrote:
> $ objdump -x /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.11.3 | grep SONAME
> SONAME libQt5Core.so.5
Note the two numbers in the SONAME. They mean two different thing. Right now,
they are equal but the
Mutz, Marc via Development wrote:
> I'd still like to deprecate them. QSDP is issuing atomic operations on
> each mutable access hurting code-gen,
Well yes, you have to use constData() or cast to const where needed. That
does not reduce QSharedDataPointer's usefulness. It is an implementation
tool
On Tue, Jun 04, 2019 at 06:38:35PM +0200, André Hartmann wrote:
> I just stumbled about the problem, that the new Gerrit removes the
> sanity review vote after a change was moved to a new destination branch.
>
> While it's probably good to remove code review votes on branch change,
> the sanity re
Konstantin Shegunov wrote:
> What about shortening the major version release time, instead of changing
> the whole model?
IMHO, major versions with source&binary compatibility need to actually live
much LONGER, not shorter. At least 20-30 years, with the time at least
doubling with every new maj
On Mon, Jun 03, 2019 at 10:59:59AM -0700, Thiago Macieira wrote:
> It can only read qmake files.
>
nope
> And it lacks the transform functions to produce an hex dump.
>
nope
___
Development mailing list
Development@qt-project.org
https://lists.qt-proje
On 2019-06-03 11:26, Lars Knoll wrote:
[...]
== QSharedDataPointer / QExplicitlySharedDataPointer ==
[...]
I see no reason at all for removing those, quite to the contrary. They
are very helpful for building refcounted classes (explicitly or
implicitly shared).
I'd still like to deprecate the
On 2019-05-30 20:35, Thiago Macieira wrote:
On Wednesday, 29 May 2019 08:13:51 PDT Olivier Goffart wrote:
[...]
> === QWaitCondition -> std::condition_variable(_any) ===
Yes.
Can't change QWaitCondition without changing QMutex. It's all or
nothing.
I believe std::condition_variable_any sh
On 2019-05-30 20:27, Thiago Macieira wrote:
On Wednesday, 29 May 2019 08:17:15 PDT Mutz, Marc via Development
wrote:
But of course, that's a fallacy, because as soon as Qt internally uses
said inline functions, every use of them by the user with a different
STL is an ODR violation and therefore
What about shortening the major version release time, instead of changing
the whole model?
Say we keep the current model, but instead of doing a major release once in
6-7 years, we fix that to 3 years with two LTS releases - one 1.5 years in,
and then the last minor version before the major release
I think that is important to mention that the Logs components are not
provided in the offline installer. It should be.
El mar., 4 jun. 2019 a las 8:10, Konstantin Tokarev ()
escribió:
>
>
> 04.06.2019, 17:01, "Volker Hilsheimer" :
> >> 04.06.2019, 16:41, "Volker Hilsheimer" :
> On 3 Jun 2019
Hi!
On Tue, 4 Jun 2019 at 13:46, Mutz, Marc via Development
wrote:
>
> Hi,
>
> This is not meant to be a summary of the thread so far, but the
> definition of a possible solution space:
>
> = The meaning of deprecation
>
> I think of deprecation as a means to tell users that the designers of
> th
Hi,
This is not meant to be a summary of the thread so far, but the
definition of a possible solution space:
= The meaning of deprecation
I think of deprecation as a means to tell users that the designers of
the deprecated API think that there is some deep flaw in the API that
makes it hard
04.06.2019, 19:40, "André Hartmann" :
> Hi all,
>
> I just stumbled about the problem, that the new Gerrit removes the
> sanity review vote after a change was moved to a new destination branch.
>
> While it's probably good to remove code review votes on branch change,
> the sanity review should n
Hi all,
I just stumbled about the problem, that the new Gerrit removes the
sanity review vote after a change was moved to a new destination branch.
While it's probably good to remove code review votes on branch change,
the sanity review should not be affected from this. Or if it is, the
sanity b
04.06.2019, 17:01, "Volker Hilsheimer" :
>> 04.06.2019, 16:41, "Volker Hilsheimer" :
On 3 Jun 2019, at 20:15, Elvis Stansvik wrote:
Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik :
> Hi Richard,
>
> I think this was asked on the interest list back in January [1].
>>
04.06.2019, 16:41, "Volker Hilsheimer"
mailto:volker.hilshei...@qt.io>>:
On 3 Jun 2019, at 20:15, Elvis Stansvik
mailto:elvst...@gmail.com>> wrote:
Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik
mailto:elvst...@gmail.com>>:
Hi Richard,
I think this was asked on the interest list back in Jan
04.06.2019, 16:41, "Volker Hilsheimer" :
>> On 3 Jun 2019, at 20:15, Elvis Stansvik wrote:
>>
>> Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik :
>>> Hi Richard,
>>>
>>> I think this was asked on the interest list back in January [1].
>>>
>>> The answer is here:
>>>
>>> https://code.qt.io/cgi
On 3 Jun 2019, at 20:15, Elvis Stansvik
mailto:elvst...@gmail.com>> wrote:
Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik
mailto:elvst...@gmail.com>>:
Hi Richard,
I think this was asked on the interest list back in January [1].
The answer is here:
https://code.qt.io/cgit/qtsdk/qtsdk.git/t
Hi everyone!
We have released Qt 5.13.0 RC today. Delta to Beta4 attached.
Target for official Qt 5.13.0 release is 13th June 2019.
br
Jani Heikkinen
Release Manager
qt5.git
247b429c3c435a62df3d6f94c96c7cd1b7c22299 Install prebuilded OpenSSL 1.1.1b for
Windows 7
qt3d:
qtactiveqt:
qtandroidextr
Excellent yes. That was a recent addition to the installer framework, very
useful for exactly that purpose.
Simon
From: Markus Haberlander
Sent: Tuesday, June 4, 2019 12:47
To: Simon Hausmann
Cc: Richard Weickelt; development@qt-project.org
Subject: Re: [Devel
Hi,
another place worth to mention:
There is a component "Logs" in the Qt installer for each Qt version, at
least for newer releases like 5.9.8 or 5.12.x. When selecting this, you get
a zip file with build and test logs for *all* prebuilt versions of Qt.
E.g. for the linux configure line of Qt 5.
Hi,
It's a little tricky, but you can reverse engineer it :)
The releases are spun from qt5.git. So if you take the 5.12.3 release, for
example then using git tag -l you can see a v5.12.3 tag in the qt5.git
repository.
A quick git show on that tag leads you to
commit 8337e20fadddf7f9c3407
Den mån 3 juni 2019 kl 20:29 skrev Richard Weickelt :
>> I would expect "Official builds configuration options
>> site:lists.qt-project.org" to bring this post up:
>> https://lists.qt-project.org/pipermail/interest/2019-January/032221.html
>> but it seems like google hasn't even indexed it.
Elvis
28 matches
Mail list logo
