03.05.2017, 21:25, "Thiago Macieira" :
> Em quarta-feira, 3 de maio de 2017, às 10:55:49 PDT, Konstantin Tokarev
> escreveu:
>> So, do you think we should update 5.6 branch of QtWebKit with wip/next
>> contents, fix qmake wrapper project to work with Qt 5.6, and raise
>> requirements to whatev
Em quarta-feira, 3 de maio de 2017, às 10:55:49 PDT, Konstantin Tokarev
escreveu:
> So, do you think we should update 5.6 branch of QtWebKit with wip/next
> contents, fix qmake wrapper project to work with Qt 5.6, and raise
> requirements to whatever it can require with Qt 5.9? That's fine with me
03.05.2017, 20:44, "Thiago Macieira" :
> Em quarta-feira, 3 de maio de 2017, às 08:03:50 PDT, Konstantin Tokarev
> escreveu:
>> I'm not sure it would be acceptable, because updated QtWebKit requires full
>> C++11 support in the compiler (gcc >= 4.9, 4.8 possible with disabling some
>> features
Em quarta-feira, 3 de maio de 2017, às 08:45:42 PDT, René J.V. Bertin
escreveu:
> On Wednesday May 03 2017 12:08:49 Edward Welbourne wrote:
> >https://testresults.qt.io/logs/qt/qtbase/74dfb52faa8370b61de9eb89947bfdd473
> >fe4986/LinuxUbuntu_15_04x86_64LinuxUbuntuTouch_15_04armv7GCCqtci-linux-Ubun
Em quarta-feira, 3 de maio de 2017, às 08:03:50 PDT, Konstantin Tokarev
escreveu:
> I'm not sure it would be acceptable, because updated QtWebKit requires full
> C++11 support in the compiler (gcc >= 4.9, 4.8 possible with disabling some
> features, or with code changes, which were not done yet).
03.05.2017, 18:05, "Adalid Claure" :
> Does this mean that at some point this new QtWebKit would be packaged with Qt
> (like in the old days)?
I hope for this (if possible, in 5.9 with Technology preview status ;)
Also note that you can already get binaries compatible with Qt 5.8.0 from
https
Does this mean that at some point this new QtWebKit would be packaged with
Qt (like in the old days)?
On Wed, May 3, 2017 at 10:25 AM, Sergio Martins
wrote:
> On 2017-05-03 15:02, Konstantin Tokarev wrote:
>
>> Remaining question is versioning. While it's fine to dub current
>> release "5.9" (bu
03.05.2017, 17:27, "Sergio Martins" :
> On 2017-05-03 15:02, Konstantin Tokarev wrote:
>> Remaining question is versioning. While it's fine to dub current
>> release "5.9" (but not 5.0, because we will have another WebKit update
>> in 5.10 time frame), using Qt versions in QtWebKit has downsid
On 2017-05-03 15:02, Konstantin Tokarev wrote:
Remaining question is versioning. While it's fine to dub current
release "5.9" (but not 5.0, because we will have another WebKit update
in 5.10 time frame), using Qt versions in QtWebKit has downsides:
1. It is not clear if 5.N+1 ships with the same
Hi all,
A lot of time has passed since original thread [1]. Lots of work was done since
then, and it took much more time than what I've originally planned, however I
think now we can use updated QtWebKit as a full replacement of our previous
branch that didn't have updates of WebKit engine sinc
Em quarta-feira, 3 de maio de 2017, às 05:08:49 PDT, Edward Welbourne
escreveu:
> Thiago Macieira wrote:
> >> In 5.8, the build deadlocks, so
> >> we can't even just disable a test.
>
> René J. V. Bertin (3 May 2017 13:28) replied:
> > How is that even possible?
>
> We don't know. And yet:
>
>
Em quarta-feira, 3 de maio de 2017, às 04:28:30 PDT, René J. V. Bertin
escreveu:
> Thiago Macieira wrote:
> > The commercial client will complain to paid support, support will
> > investigate the issue and figure out what the regression is.
>
> And if they can't reproduce it either?
Then they do
Thiago Macieira wrote:
>> In 5.8, the build deadlocks, so
>> we can't even just disable a test.
René J. V. Bertin (3 May 2017 13:28) replied:
> How is that even possible?
We don't know. And yet:
https://testresults.qt.io/logs/qt/qtbase/74dfb52faa8370b61de9eb89947bfdd473fe4986/LinuxUbuntu_15_04x
Thiago Macieira wrote:
> The commercial client will complain to paid support, support will investigate
> the issue and figure out what the regression is.
And if they can't reproduce it either?
> In 5.8, the build deadlocks, so
> we can't even just disable a test.
How is that even possible?
14 matches
Mail list logo