[Development] Remaining tools in CMAKE_INSTALL_BINDIR

[Thiago Macieira]

On Friday, 7 October 2022 10:57:52 PDT Ulf Hermann via Development wrote:
> In a parallel install the Qt5 and Qt6 QML import paths should be
> separate. If you ship your own QML modules you can in principle build
> them against both Qt5 and Qt6, separately, and install them in the
> respective import paths. But I don't know if anyone actually does that.

My question was for the developer's own plugins. Are these tools meant for the 
developer to test their QML importing their plugins? It might be surprising 
that it cannot find the plugins they've just installed to QML_PLUGIN_PATH, or 
worse, finds an older version of them.

> We made an effort to keep Qt's own QML modules source compatible between
> Qt5 and Qt6, including versions. However, there are modules that
> blatantly break compatibility. QtMultimedia and QtLocation come to mind.
> No idea if those were deprecated before they were re-created for Qt6.

Indeed, but in that case it's the plugin / module that decided to break 
compatibility. It's entirely possible for this to happen again in the 6.x 
lifetime, so that alone is not reason enough to version. I'm more worried 
about the impossibility of setting QML_PLUGIN_PATH or equivalent variable to 
load the content that the developer wants to see loaded.

> Also, qmlplugindump actually loads plugins. So, although it's almost the
> same source code you cannot use the Qt5 qmlplugindump to read Qt6
> plugins, or vice versa.

Ok, so we treat it like qtplugininfo: we install it with a versioned link.
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering