Re: [Development] Qt 6 buildsystem support requirements

2018-07-20 Thread Allan Sandfeld Jensen
On Samstag, 21. Juli 2018 07:38:10 CEST Bogdan Vatra via Development wrote: > Hi, > > În ziua de sâmbătă, 21 iulie 2018, la 05:35:48 EEST, Thiago Macieira a scris: > > Hello > > > > Having spent far too much time trying to figure out why crappy > > buildsystems > > [...] > > > 1) Ease of obten

Re: [Development] Qt 6 buildsystem support requirements

2018-07-20 Thread Thiago Macieira
On Friday, 20 July 2018 22:38:10 PDT Bogdan Vatra via Development wrote: > > b) Must be easily compiled from source on a standard system installation. > > All of its dependencies must come from the system's package manager and > > there must be no cyclic dependencies. That is, it cannot require its

Re: [Development] Qt 6 buildsystem support requirements

2018-07-20 Thread Bogdan Vatra via Development
Hi, În ziua de sâmbătă, 21 iulie 2018, la 05:35:48 EEST, Thiago Macieira a scris: > Hello > > Having spent far too much time trying to figure out why crappy buildsystems [...] > > 1) Ease of obtention > > a) Must be packaged by all major package managers where Qt 6 is expected to > be relevant.

Re: [Development] Qt 6 buildsystem support requirements

2018-07-20 Thread Thiago Macieira
On Friday, 20 July 2018 19:35:48 PDT Thiago Macieira wrote: > I'll take care of Clear Linux, but we apply the "two major distros" rule, so > I won't be first. Fedora and openSUSE already package it, so I will add it to Clear Linux. However, I am blocked by https://bugreports.qt.io/browse/QTCREATO

[Development] Qt 6 buildsystem support requirements

2018-07-20 Thread Thiago Macieira
Hello Having spent far too much time trying to figure out why crappy buildsystems cause failures in distros (like TensorFlow or libvpx - see https://plus.google.com/+ThiagoMacieira/posts/DqTKdRGfuwR ), I'd like to make sure this doesn't happen to Qt 6. For that, I'd like to add the following e

Re: [Development] Support for Windows Arm64 Desktop Target

2018-07-20 Thread Thiago Macieira
On Friday, 20 July 2018 11:08:57 PDT Thomas Miller wrote: > What's the best way to set up a review with changes in multiple submodules? > Should I just push changes for 1 submodule at a time? One submodule at a time. Don't worry about the update to qt5.git, that's done automatically. -- Thiago

Re: [Development] Support for Windows Arm64 Desktop Target

2018-07-20 Thread Thomas Miller
Thanks Maurice. I'll keep working on the changes and put them up for review when they're ready. Quick question though that I haven't seen addressed in the docs: What's the best way to set up a review with changes in multiple submodules? Should I just push changes for 1 submodule at a time? Thanks

Re: [Development] Why are my merged patches not in dev after checkout?

2018-07-20 Thread Edward Welbourne
Am Donnerstag, 19. Juli 2018 schrieb Daniel Savi: >> Now, I did a "git checkout dev" and "git rebase origin/dev" on my >> local machine that didn't have the dev branch on it before. The >> rebase command told me, that my local branch was up to date. "git >> branch" shows that I'm on "dev" Andre