[Development] build QT5.12.2 failed

2019-02-20 Thread 刘芬
Hello, When I build QT5.12.2 from source, Fatal error encountered. -- .obj\debug\multipleax.idl qt.qpa.plugin: Could not find the Qt platform plugin "windows" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this p

Re: [Development] codereview, merge please

2019-02-20 Thread Kari Oikarinen
On 21.2.2019 9.08, Martin Koller wrote: > On Freitag, 15. Februar 2019 11:08:18 CET Andy Shaw wrote: >> Since it has the +2 you can click on the "Merge patch 2 to staging" now, is >> that button showing up for you? > > So now I did merge it to staging, but I got a "Qt CI Bot" mail stating that

Re: [Development] codereview, merge please

2019-02-20 Thread Martin Koller
On Freitag, 15. Februar 2019 11:08:18 CET Andy Shaw wrote: > Since it has the +2 you can click on the "Merge patch 2 to staging" now, is > that button showing up for you? So now I did merge it to staging, but I got a "Qt CI Bot" mail stating that "Continuous Integration: Failed" https://testresul

Re: [Development] CMake Workshop Summary

2019-02-20 Thread Simon Hausmann
I tend towards Alexandru’s approach for the sake of a maximal parallel build. But it’s not evident yet whether this approach is feasible or whether perhaps the external project solution gives better results in terms of maintenance / correctness. With other modules getting wip/cmake branches I

Re: [Development] CMake Workshop Summary

2019-02-20 Thread Croitor Alexandru
This is why for Qt For Python, we've opted to make a superproject that doesn't use ExternalProejct, but rather uses add_subdirectory on each subproject. The advantage is that you can open the superproject CMakeLists.txt directly in Qt Creator, and get code completion and all the goodies for the who

Re: [Development] CMake Workshop Summary

2019-02-20 Thread Matthew Woehlke
On 13/02/2019 05.06, Simon Hausmann wrote: > We briefly discussed the topic and it's my understanding that an agreement > exists to support two types of builds: > > (1) Build a repo, install it, build the next repo, install it, etc. > (2) Have a super-project that allows building all of Q

Re: [Development] Qt QML Maintainer change

2019-02-20 Thread Robert Loehning
+1 for Ulf. Disclaimer: He's working for the same company as I do. Thank you for your work, Simon! Am 18.02.2019 um 14:25 schrieb Simon Hausmann: > Hi, > > I'd like to step down as the maintainer of the Qt QML module and pass the > torch on to Ulf Hermann. > > He has been contributing to the m

Re: [Development] "font emojis", where are they processed?

2019-02-20 Thread René J . V . Bertin
Tor Arne Vestbø wrote on 20190220::11:58:33 re: "Re: [Development] "font emojis", where are they processed?" No problem, bouncing this back to the ML then to see if someone else picks it up. R. > >> On 20 Feb 2019, at 10:49, René J.V. Bertin wrote: >> &

[Development] HEADS-UP: Branching from '5.12' to '5.12.2' done

2019-02-20 Thread Jani Heikkinen
Hi! Final downmerge from '5.12' -> '5.12.2' is now done and all fixes targeted to Qt 5.12.2 release must be done in '5.12.2' and '5.12' is for Qt 5.12.3 from now on. Staging in '5.12.2' is restricted to release team only. br, Jani From: Development on

[Development] 3rd party component updates for Qt 5.13

2019-02-20 Thread Jani Heikkinen
Hi, It is time to start updating 3rd party components for Qt 5.13. There is follow up user story (https://bugreports.qt.io/browse/QTBUG-72610) containing sub tasks for each qt module. Please start working with this now & finalize this latest before Qt 5.13 beta3 (but preferably as early as poss