Re: [Development] Enabling private features for separate modules

On Montag, 19. Juni 2017 11:52:12 CEST Alexander Volkov wrote: > Hi, > > I build qtwebengine as a separate module. > What is the right way to enable system-ffmpeg feature? > It's not auto-detected: > "system-ffmpeg": { > "label": "ffmpeg", > "autoDetect":

Re: [Development] Enabling private features for separate modules

On Mon, Jun 19, 2017 at 01:52:59PM +0300, Alexander Volkov wrote: > 19.06.2017 12:53, Oswald Buddenhagen пишет: > > On Mon, Jun 19, 2017 at 12:52:12PM +0300, Alexander Volkov wrote: > >> Hi, > >> > >> I build qtwebengine as a separate module. > >> What is the right way to enable system-ffmpeg

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

On Monday, 19 June 2017 03:48:42 PDT Morten Sørvig wrote: > - Can we self-test the network interface and QSKIP if it’s not in working > order? That's the test itself: it tries to send a packet back to itself and see if it arrives. > - We can blacklist on CI only: >

Re: [Development] Enabling private features for separate modules

19.06.2017 20:06, Oswald Buddenhagen пишет: On Mon, Jun 19, 2017 at 01:52:59PM +0300, Alexander Volkov wrote: 19.06.2017 12:53, Oswald Buddenhagen пишет: On Mon, Jun 19, 2017 at 12:52:12PM +0300, Alexander Volkov wrote: Hi, I build qtwebengine as a separate module. What is the right way to

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

Thiago Macieira (16 June 2017 22:23) > QDEBUG : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) > QHostAddress("fe80::250:56ff:feab:4818%eth1") > FAIL! : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) > '(neutralReadSpy.count() > 0)' returned FALSE. () > Loc: [../tst_qudpsocket.cpp(1600)] I

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

Hi, I've checked that all iptables for IPv4 and IPv6 are empty. Simon From: Development on behalf of Edward Welbourne Sent: Monday, June 19, 2017 11:36:19 AM To: Thiago

[Development] Enabling private features for separate modules

Hi, I build qtwebengine as a separate module. What is the right way to enable system-ffmpeg feature? It's not auto-detected: "system-ffmpeg": { "label": "ffmpeg", "autoDetect": false, "condition": "libs.ffmpeg && features.system-opus &&

Re: [Development] Enabling private features for separate modules

On Mon, Jun 19, 2017 at 12:52:12PM +0300, Alexander Volkov wrote: > Hi, > > I build qtwebengine as a separate module. > What is the right way to enable system-ffmpeg feature? > you use qmake [usual qmake args] -- [configure args] ___ Development

[Development] Flaky auto tests on macOS 10.12

Hi all, After a few successful qt5.git CI rounds, auto tests were enabled for macOS 10.12 in the CI last week. [*] Even though many flaky auto tests had been already blacklisted on macOS 10.12 earlier (https://bugreports.qt.io/browse/QTBUG-58968), it became nearly impossible to integrate any

[Development] Qt 5.9.1 branching finalized

Hi all, Final downmerge is now done and '5.9' is for '5.9.2' from now on. We will start doing Qt 5.9.1 "rc" now to see if there is still some issue to be fixed before official release. But the target is that current '5.9.1' is final content for the release so please not try to get in any

Re: [Development] First Qt 5.9.1 snapshot available

> -Original Message- > From: André Hartmann [mailto:aha_1...@gmx.de] > Sent: sunnuntai 18. kesäkuuta 2017 18.25 > To: Jani Heikkinen ; development@qt-project.org; > inter...@qt-project.org > Cc: releas...@qt-project.org > Subject: Re: [Development] First Qt 5.9.1

Re: [Development] Flaky auto tests on macOS 10.12

It is the intention that we do this. But we're constantly running, not beside our horse, but after it. We have just begun activating ourselves to discuss about 5.10 platforms and we have FF coming up in two weeks (counting out July here). It took months to blacklist all the cases for 10.12

[Development] Qt 5.9.1 initial change files available

Hi all initial change files available, see https://codereview.qt-project.org/#/q/message:%22Add+changes%22+branch:5.9.1,n,z Maintainers: Please do needed modifications & get approval as soon as possible (today/latest tomorrow) br, Jani Heikkinen Release Manager

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

> On 16 Jun 2017, at 23:21, Thiago Macieira wrote: > > On Friday, 16 June 2017 13:23:07 PDT Thiago Macieira wrote: >> QDEBUG : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) >> QHostAddress("fe80::250:56ff:feab:4818%eth1") >> FAIL! :

Re: [Development] Enabling private features for separate modules

19.06.2017 13:59, Dominik Holland пишет: $ qmake -- -system-ffmpeg ***Unknown option -system-ffmpeg I think it needs to be: qmake -- --enable-system-ffmpeg if you want to add your own options you can also add a "commandline" section to configure.json It also doesn't work. Somehow this way of

Re: [Development] Enabling private features for separate modules

19.06.2017 12:53, Oswald Buddenhagen пишет: On Mon, Jun 19, 2017 at 12:52:12PM +0300, Alexander Volkov wrote: Hi, I build qtwebengine as a separate module. What is the right way to enable system-ffmpeg feature? you use qmake [usual qmake args] -- [configure args] $ qmake --

Re: [Development] Enabling private features for separate modules

Am 06/19/2017 um 12:52 PM schrieb Alexander Volkov: > 19.06.2017 12:53, Oswald Buddenhagen пишет: >> On Mon, Jun 19, 2017 at 12:52:12PM +0300, Alexander Volkov wrote: >>> Hi, >>> >>> I build qtwebengine as a separate module. >>> What is the right way to enable system-ffmpeg feature? >>> >> you

Re: [Development] Flaky auto tests on macOS 10.12

> On 19 Jun 2017, at 13:09, Tony Sarajärvi wrote: > > It is the intention that we do this. But we're constantly running, not beside > our horse, but after it. We have just begun activating ourselves to discuss > about 5.10 platforms and we have FF coming up in two weeks