[Development] Build system for Qt 6

Edward Welbourne edward.welbourne at qt.io
Mon Nov 12 15:56:58 CET 2018

On 10/30/18 12:16 PM, Bogdan Vatra via Development wrote:
>>> d) While c.1 and c.2 can be fixed with some effort, here we have bigger
>>> problems:
>>>    - Instread to port QBS to QML JS in the first second when QtScript was
>>>      deprecated, they fork it! I know that back then QML JS needed
>>>      some love, but instead to collaborate with QML JS folks they
>>>      decided keep using QtScript!

În ziua de luni, 12 noiembrie 2018, la 15:06:00 EET, Joerg Bornemann a scris:
>> QtScript was never forked. It even was included as git submodule at some
>> point. Unaltered.

Bogdan Vatra (12 November 2018 14:39)
>  This is very funny! did you included it as git submodule just because
> you like submodules?

Including it as a sub-module is exactly what qt5.git did, so qbs was
using it exactly the way qt5 used it.  This is not a fork: a fork has
separate development that isn't being merged back to the upstream.  If
the QBS team had any patches for QtScript or the QML parser, using them
as sub-modules meant that their fixes went into the upstream module, so
was used by Qt5 as soon as it was in use by QBS (give or take qt5's
integration delays).  Please don't misrepresent the history.


More information about the Development mailing list