[Qbs] Future of Qbs
enmarantispam at gmail.com
Wed Oct 31 11:45:10 CET 2018
I have added a new field to that table: "QBS used since"
This is kind of relevant. If you've put your project in previously, please
On Wed, Oct 31, 2018 at 1:30 PM NIkolai Marchenko <enmarantispam at gmail.com>
> I would like to remind in this thread that we have a list going to
> hopefully change TQtC's image of qbs adoption.
> Please post your qbs projects there:
> On Wed, Oct 31, 2018 at 1:09 PM Christian Kandeler <
> Christian.Kandeler at qt.io> wrote:
>> On Wed, 31 Oct 2018 06:51:43 +0100
>> Richard Weickelt <richard at weickelt.de> wrote:
>> > It would be great if the TQtC could clarify what is planned for the next
>> > feature release and why.
>> That's easy: The release will simply contain everything that has been
>> done since 1.12, i.e. all patches that have already landed in master and
>> some that are almost finished (plus possible community contributions). The
>> most noteworthy improvements will be job pools and proper Android support
>> for Qt apps.
>> > - How does the release process of Qbs work?
>> It's not particularly involved. Source packages are created with git,
>> the Windows binaries (including the chocolatey package) are built by
>> qbs itself. There is a public docker image that automates this task;
>> see https://doc.qt.io/qbs/building-qbs.html#building-release-packages.
>> > - Are there parts in the codebase that make maintenance difficult and
>> > that could be simplified?
>> The module loader, which does the low-level part of resolving a project,
>> is very complicated and brittle. Changes in that area typically pose the
>> biggest challenge. The rest of the code, while not necessarily trivial, can
>> be touched without fear of losing one's sanity.
>> > Maybe parts duplicating Qt code that should
>> > be rebased onto Vanilla Qt?
>> Why would there be?
>> Qbs mailing list
>> Qbs at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Qbs