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

2019-03-19 Thread Jedrzej Nowacki
On Tuesday, March 19, 2019 7:55:53 AM CET Uwe Rathmann wrote: > 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

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

2019-03-19 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

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

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

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

2019-03-18 Thread Uwe Rathmann
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

2019-03-18 Thread Thiago Macieira
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] Continuous Integration for 3rd party projects using Qt

2019-03-17 Thread Lorn Potter
On 17/3/19 11:54 PM, Uwe Rathmann wrote: Hi, all arguments for doing Continuous Integration for Qt ( https:// blog.qt.io/blog/2016/08/08/coin-continuous-integration-for-qt/ ) are also valid for 3rd party code using Qt. F.e. with Qwt ( https://qwt.sourceforge.io ) I'm supporting trillions of

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

2019-03-17 Thread Denis Kormalev
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. -- Regards, Denis Kormalev > On Mar 17, 2019, at 9:03 AM, Bernhard B wrote: > > Why not use

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

2019-03-17 Thread Bernhard B
Why not use one of the continous integration services like travis-ci or circle-ci? Cheers, Bernhard Uwe Rathmann schrieb am So., 17. März 2019, 14:55: > Hi, > > all arguments for doing Continuous Integration for Qt ( https:// > blog.qt.io/blog/2016/08/08/coin-continuous-integration-for-qt/ )