[Development] Qt 6 buildsystem support requirements

Tobias Hunger tobias.hunger at gmail.com
Sun Jul 22 19:34:13 CEST 2018

Hi Thiago,

On Sun, Jul 22, 2018, 17:35 Thiago Macieira <thiago.macieira at intel.com>

> >  A) works with IDE(s) -- preferably more than one
> Hello Tobias
> The fact that we have an IDE of ours means this one should be reasonably
> easy
> to address, as we can make that IDE work with the tool. So long as the
> tool is
> actually toolable, of course.

This is a matter of resources and what we want to spend those on.

Creator needs first class support for qmake for years to come. It also
needs first class support for CMake as that is what people out there
actually use. These two are set for the foreseeable future.

When we have a decision on what Qt will use going forward, then that will
be added to the mix.

"More than one" would be quite a challenge.

We can not expect people to drop their preferred set of tools to work on
Qt. That is a sure-fire way to reduce contributions from outside of our
core community.

>  B) Should be easy to hook in static and dynamic code analyzer tools
> Can you elaborate?

Most build tools offer to create a build_commands.json file so that some of
the clang tools can be used easily. I expect that from any build tool

Meson offers a "build with address sanitisation" option (and similar ones
for UBSAN, etc.) that can just turn on for your project. I would love that,
but at the very least compiler-based tools like ASAN and UBSAN should be
easy to enable with good documentation on how to do so.

A build tool with a track record of empowering developers by making new
tools easy to use on existing projects would be welcome.

Best regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20180722/5e03694a/attachment.html>

More information about the Development mailing list