Closed pzhlkj6612 closed 1 year ago
Upstream, we started testing install-tool
with both QtIFW and QtCreator in https://github.com/miurahr/aqtinstall/pull/443 and https://github.com/miurahr/aqtinstall/pull/451. The following bash code will run command line binaries included with both tools, and will cause the job to fail if the tools were not properly installed:
qt_ifw_bin_path="./Qt/Tools/QtInstallerFramework/*/bin/"
case $(uname -s) in
Darwin*) qt_creator_bin_path="./Qt/Qt Creator.app/Contents/MacOS/";;
*) qt_creator_bin_path="./Qt/Tools/QtCreator/bin/";;
esac
# Check if QtIFW is installed
ls "${qt_ifw_bin_path}"
"${qt_ifw_bin_path}archivegen" --version
# Check if QtCreator is installed: QtCreator includes the CLI program 'qbs' on all 3 platforms
ls "${qt_creator_bin_path}"
"${qt_creator_bin_path}qbs" --version
The current CI workflow installs Qt Installer Framework and Qt Creator but does not test them:
https://github.com/jurplel/install-qt-action/blob/59f08e42a726f2bd91e36457a99d34dc1aff54cb/.github/workflows/test.yml#L27-L32
Since aqtinstall v1 will silently fail when the specified version of a tool does not exist, the test in the CI workflow does not cover the failure of the tool installation.
I think we need to test the tools when using aqtinstall v2, too. See also #114 .