Re: [Development] Continuous Integration for 3rd party projects using Qt

2019-03-18 Thread Uwe Rathmann
Hi all, in the end all advice goes into the direction of using one of the standard services in combination with using my own brain when working on the code. Unfortunately nobody pointed out a realistic way how a 3rd party project could make use of the infrastructure used by the Qt project nor

Re: [Development] Continuous Integration for 3rd party projects using Qt

2019-03-18 Thread Thiago Macieira
On Sunday, 17 March 2019 23:49:09 PDT Uwe Rathmann wrote: > Hi, > > thanks for the all the hints in this thread - I will check them if I > can't find a service, that is more specific: > > a) > > The very first of my problems is to know about the platforms I need to > test. I guess the list of al

Re: [Development] QML preprocessor

2019-03-18 Thread Alberto Mardegan
On 18/03/19 12:11, Pierre-Yves Siret wrote: > This can be done with QQmlFileSelector : > >     QQmlApplicationEngine engine; >     QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get(&engine); > > #if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0) >     qmlFileSelector->setExtraSelectors({"5.12"}

Re: [Development] Continuous Integration for 3rd party projects using Qt

2019-03-18 Thread Denis Kormalev
Different compilers and qt versions are easily solvable with multiple docker images (that can be generated using single Dockerfile with arguments). In this case in CI itself all you need is just to build in each of them in common way (ideally you just put your build script as entry point and run

Re: [Development] QStringLiteral is broken(ish) on MSVC (compiler bug?)

2019-03-18 Thread Giuseppe D'Angelo via Development
On 18/03/2019 17:02, Matthew Woehlke wrote: On 16/03/2019 12.13, Giuseppe D'Angelo via Development wrote: What I meant is this: during phase 5 and 6, are string literals simply sequences of symbols from a set, or are they already encoded in some encoding? From my reading, it's the former (the ex

Re: [Development] QStringLiteral is broken(ish) on MSVC (compiler bug?)

2019-03-18 Thread Matthew Woehlke
On 16/03/2019 12.13, Giuseppe D'Angelo via Development wrote: > What I meant is this: during phase 5 and 6, are string literals > simply sequences of symbols from a set, or are they already encoded > in some encoding? From my reading, it's the former (the execution > character set is just this --

Re: [Development] Nominating Brett Stottlemeyer for Approver status

2019-03-18 Thread Stottlemyer, Brett (B.S.)
I'm the maintainer for QtRO (per the wiki page) already. But I only have +2 rights on the remote objects module, none of the others (which I didn't realize until later was unusual). Thanks for the nomination (and votes). If approved, I'll certainly treat the pr

Re: [Development] Nominating Brett Stottlemeyer for Approver status

2019-03-18 Thread Lars Knoll
Obvious +1, I thought he had those rights already since a long time. Cheers, Lars On 18 Mar 2019, at 10:07, Simon Hausmann mailto:simon.hausm...@qt.io>> wrote: +1 to the slam dunk of making Brett approver :). He's great to work with, always positive and I certainly trust him on the approval p

Re: [Development] Nominating Brett Stottlemeyer for Approver status

2019-03-18 Thread Bogdan Vatra via Development
+1 În ziua de luni, 18 martie 2019, la 10:05:22 EET, Ville Voutilainen a scris: > Brett is the maintainer of Qt Remote Objects. Thus he should be > documented as a maintainer, and should also be an approver. Brett has > been effectively maintaining QRO since 2014, so it seems like a slam > dunk

Re: [Development] QML preprocessor

2019-03-18 Thread Samuel Stirtzel via Development
Am So., 17. März 2019 um 13:35 Uhr schrieb Alberto Mardegan : > > Hi there! > When developing a QML module for the greater public one wants to > provide a source package that can be built on multiple Qt versions. > However, QML's lack of a preprocessor makes this rather cumbersome. > > Suppose th

Re: [Development] QML preprocessor

2019-03-18 Thread Pierre-Yves Siret
Hello, This can be done with QQmlFileSelector : QQmlApplicationEngine engine; QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get(&engine); #if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0) qmlFileSelector->setExtraSelectors({"5.12"}); #endif engine.load(QUrl(QStringLiteral("qr

Re: [Development] Nominating Brett Stottlemeyer for Approver status

2019-03-18 Thread Simon Hausmann
+1 to the slam dunk of making Brett approver :). He's great to work with, always positive and I certainly trust him on the approval process. Simon From: Development on behalf of Ville Voutilainen Sent: Monday, March 18, 2019 9:05 To: development@qt-project.or

Re: [Development] Continuous Integration for 3rd party projects using Qt

2019-03-18 Thread Volker Hilsheimer
On 18 Mar 2019, at 07:49, Uwe Rathmann mailto:uwe.rathm...@tigertal.de>> wrote: Hi, thanks for the all the hints in this thread - I will check them if I can't find a service, that is more specific: a) The very first of my problems is to know about the platforms I need to test. I guess the list

Re: [Development] QML preprocessor

2019-03-18 Thread Albert Astals Cid via Development
El diumenge, 17 de març de 2019, a les 13:34:09 CET, Alberto Mardegan va escriure: > Hi there! > When developing a QML module for the greater public one wants to > provide a source package that can be built on multiple Qt versions. > However, QML's lack of a preprocessor makes this rather cumber

[Development] Nominating Brett Stottlemeyer for Approver status

2019-03-18 Thread Ville Voutilainen
Brett is the maintainer of Qt Remote Objects. Thus he should be documented as a maintainer, and should also be an approver. Brett has been effectively maintaining QRO since 2014, so it seems like a slam dunk to give him the rights. ___ Development mail