[Qt-creator] test discovery

[Eike Ziller]

> On Jan 5, 2021, at 19:31, Alessandro Portale <Alessandro.Portale at qt.io> wrote:
> 
> Von: Qt-creator <qt-creator-bounces at qt-project.org> im Auftrag von André Pönitz <apoenitz at t-online.de>
> Gesendet: Dienstag, 5. Januar 2021 19:18
> An: Stefan Seefeld <stefan at seefeld.name>
> Cc: qt-creator at qt-project.org <qt-creator at qt-project.org>
> Betreff: Re: [Qt-creator] test discovery
> 
> > Can't I just compile the plugin (using some public qt-creator Plugin API) ?
> > Sorry if I'm displaying my ignorance here, but I assumed that qt-creator
> > supporting "plugins" implied that those plugins could be managed (including
> > built) independently from qt-creator.
> 
> The Qt Creator plugin SDK is there for that.
> 
> Shameful plug of my talk about that: https://youtu.be/G73umuER5dA?t=1432

Yes - and no.

Qt Creator doesn’t provide source or binary compatibility between minor versions, so a plugin that was written for 4.15 has high chances not to compile without adaptations for 4.14. That would even be the case if Qt Creator provided backward source compatibility, since a plugin for 4.15 can still use API that didn’t exist in 4.14. Backporting never is a guaranteed thing.

And note that “support for ctest” is not a separate plugin - it is an update to an existing plugin (AutoTest), which makes incompatibility between Qt Creator versions even more probable. Also the AutoTest plugin is part of the regular Qt Creator source bundle and from the buildsystem point of view not made to be compiled separately from the rest of Qt Creator.

Br, Eike

-- 
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.ziller at qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B