Am Freitag, 20. Mai 2016, 14:23:51 schrieb Thiago Macieira:
> Em quarta-feira, 18 de maio de 2016, às 15:04:24 PDT, Kai Koehne escreveu:
> > > So, an updated tarball for qtquick1 for 5.6 would be really much
> > > appreciated (so that it works with 5.6.x and 5.7.x)
> >
> > It's the first time I he
Em quarta-feira, 18 de maio de 2016, às 15:04:24 PDT, Kai Koehne escreveu:
> > So, an updated tarball for qtquick1 for 5.6 would be really much
> > appreciated (so that it works with 5.6.x and 5.7.x)
>
> It's the first time I hear someone asking for a tarball for QtQuick1.
We WILL NOT provide a
Hi Ossi,
apologies I have a set of changes now integrating that have been
fighting with the CI for a few days which now look to be going through.
Should I do another 5.7 -> 5.7.0 merge after they land? They need to get
in to fix some P0 issues in Qt 3D.
Cheers,
Sean
On 20/05/2016 18:39, O
5.7.0 is fully (*) branched now. staging is limited to the release team.
as usual, i'm taking retargeting requests for tardy changes.
(*) actually, it's not. webengine is still integrating something since
half a day.
On Fri, May 13, 2016 at 01:36:30PM +0200, Oswald Buddenhagen wrote:
> The 5.7.0
Hi,
Are there any known issues with QToolBar Qt5 win32?
We've (LMMS) a downstream bug and I'm trying to isolate the cause.
https://github.com/LMMS/lmms/issues/2767
- It only happens with Qt5
- It only happens with QToolBar
- We have the QToolBar in a QMdiSubwindow/QWidget, not the
On Friday 20 May 2016 07:40:19 Thiago Macieira wrote:
> Em sexta-feira, 20 de maio de 2016, às 08:08:46 PDT, Denis Shienkov
escreveu:
> > Hi guys,
> >
> > you are talking about:
> >
> > * https://bugreports.qt.io/browse/QTCREATORBUG-16277
> >
> > * https://bugreports.qt.io/browse/QBS-974
> >
>
Em sexta-feira, 20 de maio de 2016, às 15:32:38 PDT, Joerg Bornemann escreveu:
>- load qtbase.pro (or any other Qt module) in Qt Creator with the Kit
> corresponding to that Qt
You may want to select src/src.pro or a closer .pro to what you want. No point
in waiting for everything to be re-c
Em sexta-feira, 20 de maio de 2016, às 08:08:46 PDT, Denis Shienkov escreveu:
> Hi guys,
>
> you are talking about:
>
> * https://bugreports.qt.io/browse/QTCREATORBUG-16277
>
> * https://bugreports.qt.io/browse/QBS-974
>
> ?
I'm not because I don't use QBS.
--
Thiago Macieira - thiago.maciei
On 20/05/2016 08:13, Denis Shienkov wrote:
I want to know, is it possible to build/debug the qtbase's parts from
the QtC?
Sure! I usually do something like this:
- initially configure and build Qt on the console
- add this Qt build in Qt Creator's build settings (Qt Version and Kit)
- lo
+1
Am 20.05.2016 um 15:09 schrieb Shawn Rutledge:
+1
On 20 May 2016, at 15:00, Robin Burchell wrote:
+1 :)
On Fri, May 20, 2016, at 02:49 PM, Simon Hausmann wrote:
Hi,
I would like to nominate Frank for approver status. He has done a fair
bit of surgery in the QML engine and also seems t
+1
> On 20 May 2016, at 15:00, Robin Burchell wrote:
>
> +1 :)
>
> On Fri, May 20, 2016, at 02:49 PM, Simon Hausmann wrote:
>> Hi,
>>
>>
>> I would like to nominate Frank for approver status. He has done a fair
>> bit of surgery in the QML engine and also seems to be active on
>> qtopcua/ser
+1 :)
On Fri, May 20, 2016, at 02:49 PM, Simon Hausmann wrote:
> Hi,
>
>
> I would like to nominate Frank for approver status. He has done a fair
> bit of surgery in the QML engine and also seems to be active on
> qtopcua/serialbus.
>
>
> I appreciate his input on my patches and I trust him to
+1
Cheers,
Lars
From: Development
mailto:development-bounces+lars.knoll=qt...@qt-project.org>>
on behalf of Simon Hausmann mailto:simon.hausm...@qt.io>>
Date: Friday 20 May 2016 at 14:49
To: Qt development mailing list
mailto:development@qt-project.org>>
Subject: [Development] Nominating Frank
Hi,
I would like to nominate Frank for approver status. He has done a fair bit of
surgery in the QML engine and also seems to be active on qtopcua/serialbus.
I appreciate his input on my patches and I trust him to responsibly review.
Simon
___
Dev
Hi,
Just a reminder that you _cannot_ remove noexcept
(Q_DECL_NOTHROW/Q_DECL_NOEXCEPT) nor constexpr
(Q_DECL_CONSTEXPR/Q_DECL_RELAXED_CONSTEXPR) from functions that are under SC
constraints. Adding them is ok, but removing or downgrading them from NOTHROW
to NOEXCEPT or from CONSTEXPR to RELAX
No, I didn’t see that. Thanks. :)
From: Alexander Nassian [mailto:nass...@bitshift-dynamics.de]
Sent: Friday, 20 May 2016 11:15 AM
To: Mitch Curtis
Cc: development@qt-project.org
Subject: Re: [Development] Internal compiler error when building dev branch of
qtbase with MSVC2015 on Windows 10
Do
A-ha, thanks. :)
> -Original Message-
> From: Laszlo Agocs
> Sent: Friday, 20 May 2016 11:16 AM
> To: Mitch Curtis ; development@qt-project.org
> Subject: RE: [Development] Internal compiler error when building dev
> branch of qtbase with MSVC2015 on Windows 10
>
> Yes. Same problem I com
Yes. Same problem I complained about on IRC a few days ago. I was using VS2015
Update 1 then. Installing VS2015 Update 2 fixed it. The CIs have Update 2
installed as well.
BR,
Laszlo
-Original Message-
From: Development
[mailto:development-bounces+laszlo.agocs=qt...@qt-project.org] On
Do you know this and did you already tried the suggested steps to fix?
https://support.microsoft.com/en-us/kb/305980
Beste Grüße / Best regards,
Alexander Nassian
> Am 20.05.2016 um 11:11 schrieb Mitch Curtis :
>
> Is anyone else able to reproduce this? I configured Qt with the following
> arg
Hi,
Trying to submit a simple patch to Qt 3D we are hitting a weird compilation
error on Android CI configurations. The change is:
https://codereview.qt-project.org/#/c/157592/
and the compilation errors can be seen in full at:
http://testresults.qt.io/logs/qt/qt3d/489c6abe13e098eb87fa2c0a8639
Is anyone else able to reproduce this? I configured Qt with the following
arguments (shadow build):
-debug -developer-build -opensource -confirm-license -nomake tests -nomake
examples -opengl desktop
If I use nmake instead of jom, the only error comes from qlogging.cpp.
I've attached the outpu
21 matches
Mail list logo
