On Tue, 8 Jan 2019 at 02:42, Edward Welbourne <edward.welbou...@qt.io> wrote: > > On Mon, 17 Dec 2018 at 21:43, Jean-Michaël Celerier wrote: > >> But in this day and age where docker works everywhere I don't really > >> see the point in fighting to make windows behave like a proper unix > >> system, just write a dockerscript that does your cross-compile job. > > Christian Gagneraud (17 December 2018 13:50) > > What do you mean by 'everywhere'? Native Windows dockers are still > > experimental, and i haven't heard of native MacOS docker yet (might > > have missed smth). > > I can't speak for "everywhere"; but we've found that docker works > cross-platform enough for the needs of our on-going work to replace the > monolithic net-test-server currently used to test network-related code: > > https://codereview.qt-project.org/240564 - macOS > https://codereview.qt-project.org/246535 - MS-Win > > So there is at least some grounds to hope docker can solve the > cross-compilation problems Jean-Michaël had in mind.
Not sure to understand your point, AFAIU (and i had a quick look at the commits above), you're using "docker for windows" and "docker for mac". These 2 run a Linux VM on Windows/Mac in which a Linux docker server is running, so at the end you're running Linux docker inside a Linux VM on Windows/Mac, not a Windows/Mac "native docker image". I do not see how it can helps with cross compiling... From my POV, i would like to see docker solves native builds, not cross builds. Using Linux docker images for network integration testing is a very good idea, thought. Now, things get complicated since the introduction of "native" Windows containers, that is a pure "Windows" docker containers running on Windows 10 (10 GB for a core image). So far MacOS "native" docker containers don't exists yet. Coin uses Nebula to manage VMs of all sorts (that's my understanding), and i think that the Qt Company did a mistake here: Forget about custom CI, focus on custom build system (after all that is the topic of this thread). My own, cheap/useless opinion is that the Qt company should have contacted gitlab or the like... Look at what they did with Drupal. Chris. _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
