[Development] Remaining tools in CMAKE_INSTALL_BINDIR
Thiago Macieira
thiago.macieira at intel.com
Thu Oct 6 21:00:14 CEST 2022
For the tools below, please answer:
1) are they meant to be run by the user or developer, from a command-line?
2) are they equivalent to their Qt 5 version, if it exists? That is, can the
Qt 6 tool be used where the Qt 5 one was, with Qt 5 input files if any, and
produce output that Qt 5 will understand / operate correctly with?
For anything that I could answer Yes to both or for which a "6"-suffixed copy
exists (qmake6, qtdiag6, qtpaths6), I've already excluded from the listing.
If the answer is Yes to both questions, we keep it in the bin dir.
If the answer is Yes to the first question but No to the second, let's make
sure a version with a "6" suffix exists (e.g., missing for qtplugininfo).
If the answer is No to the first question, please move the tool to libexec.
All tools in the bin dir must support --help and --version; optional but
recommended for the libexec ones too.
Android tools:
androiddeployqt
androidtestrunner
QtQuick3D:
balsam
balsamui
materialeditor
meshdebug
shapegen
Linguist file conversion:
lconvert
lrelease
lupdate
GUI / OpenGL:
qdistancefieldgenerator
qsb
shadergen
QML related:
qml
qmldom
qmleasing
qmlformat
qmljs
qmllint
qmlls
qmlplugindump
qmlpreview
qmlprofiler
qmlscene
qmltc
qmltestrunner
qmltime
Build system:
qt-cmake
qt-cmake-private
qt-cmake-private-install.cmake
qt-cmake-standalone-test
qt-configure-module
Documentation:
qdoc
Other, misc:
instancer (tool does not support --help)
qtplugininfo
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
More information about the Development
mailing list