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

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 all operating system and compiler combinations can be found somewhere in

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

On Sunday, 17 March 2019 11:05:08 PDT Denis Kormalev wrote: > Travis can cover macosx, linux (and using docker it can cover different > environments/compilers and packaging for various distribs) and android > (with linux as host). Appveyor can cover Windows builds. Those two are what I use for

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

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

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

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] Continuous Integration for 3rd party projects using Qt

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

Re: [Development] QML preprocessor

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

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

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

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

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

Re: [Development] QML preprocessor

Hello, This can be done with QQmlFileSelector : QQmlApplicationEngine engine; QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get(); #if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0) qmlFileSelector->setExtraSelectors({"5.12"}); #endif

Re: [Development] Nominating Brett Stottlemeyer for Approver status

+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 >

Re: [Development] Nominating Brett Stottlemeyer for Approver status

+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:

Re: [Development] QML preprocessor

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

[Development] Nominating Brett Stottlemeyer for Approver status

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

Re: [Development] QML preprocessor

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

Re: [Development] Nominating Brett Stottlemeyer for Approver status

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

Re: [Development] Nominating Brett Stottlemeyer for Approver status

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