[Development] Build system for Qt 6

NIkolai Marchenko enmarantispam at gmail.com
Tue Oct 30 11:25:54 CET 2018


> Yes and this is relevant if it is relevant for the maintainers of Qbs. Do
we have a statement from them so far ?

We have a confirmation from Lars that QtCreator is dropping qbs support in
a year.
That basically reads "qbs dead as there will be no IDE supporting it left".

On Tue, Oct 30, 2018 at 1:21 PM Uwe Rathmann <Uwe.Rathmann at tigertal.de>
wrote:

> On Tue, 30 Oct 2018 09:59:28 +0100, Olivier Goffart wrote:
>
> > What Lars said, if I read the email properly, is that the Qt Company
> > does not see a business value in developing it further.
>
> Yes and this is relevant if it is relevant for the maintainers of Qbs. Do
> we have a statement from them so far ?
>
> > But the project is open source and the code is there and anyone is free
> > to take over if they are interested in it.
>
> In case a maintainer decides to step down the normal process would be to
> find a new one. Only if this is not possible further steps have to be
> taken.
>
> Using Qbs for building Qt has been discussed here and lead to a solid
> decision against it. Obviously then the Qt company decided not to work on
> this code anymore - so far so good.
>
> But deprecating Qbs as a tool for building user projects is absolutely
> not covered by this discussion and if there was a more related one I seem
> to have missed it.
>
> This all has a lot to do with the question if the Qt Company sees itself
> as being a member or the owner of the Qt project. If we really want to be
> a community project, then the process of inventing and deprecating
> modules has to become more independent.
>
> Uwe
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20181030/d2cc1e61/attachment.html>


More information about the Development mailing list