- Luigi Raiano
- Templates for app deployment and installer creation of SW developed using Qt
- Qt Creator
- Qt installer Framework (to be installed when installing Qt)
The app deployment allows the user to launch the application executable without the need of compiling and running the code from Qt Creator.
- From Start menu select and open Qt MinGW:
Qt -> Qt ${version} (MinGW ${version} 64-bit)
- Go to ExampleProject folder:
cd ${path_to_ExampleProject}
- Create a new folder named
deploy
mkdir deploy
- Copy
${ExampleProject}.exe
frombuild/release
todeploy
- Go to deploy folder:
cd deploy
- Add all necessary libraries for launching
${ExampleProject}.exe
without the need of compilying the code. To this aim, launch the following command from the MinGW shell:
windeployqt.exe --quick .
- All necessary libraries will be added to deploy folder allowing to launch the the Orchestrator GUI directly from the executable file.
- Go to ExampleProject folder:
cd ${path_to_ExampleProject}
- Create a new folder named
deploy
mkdir deploy
- Copy the
${ExampleProject}.app
todeploy
cp build/${ExampleProject}.app deploy/${ExampleProject}.app
- Launch deployment:
/Applications/Qt/${Qt_Version}/clang_64/bin/macdeployqt ${ExampleProject}.app -dmg
- After completion, a file entitled
${ExampleProject}.dmg
will appear withindeploy
folder. Open this file and drag-and-drop${ExampleProject}.app
to yourApplications
system dir.
The SW installer allows the user to install all required libraries and components to launch the App without the need of receiving the source code.
- Deploy the application using the App deployment on Windows guidelines.
- Go to Desktop and create a new folder entitled
${ExampleProject}Installer
. - Here, create two subfolders entitled
config
andpackages
. - Within
config
create aconfig.xml
. - Within
packages
create a new subfolder, entitled:${ExampleProject}
. Here, create two further subfolders,data
andmeta
. data
folder contains all files to be installed, e.g. thedeploy
folder, configuration files, logos, etc. Do not put here the source code if you do not want to provide it. As golden rule, add all data to be installed within a subfolder ofdata
namedwin64
.meta
folder contains scripts and files for generating the installer with its GUI. Add here also additional files, such as the license to be accepted.
All componetes are now ready and it is time to create the installer file. To this aim:
- Open a terminal shell
- Go to
${ExampleProject}Installer
folder, i.e. whereconfig
andpackages
have been created:
cd ${path_to_${ExampleProject}Installer}
- Launch
QtInstallerFramework
:
C:\Qt\Tools\QtInstallerFramework\${QtInstallerFramework_version}\bin\binarycreator.exe -c config\config.xml -p packages ${ExampleProject}Installer.exe
- At the end of the project,
${ExampleProject}Installer.exe
will appear in${path_to_${ExampleProject}Installer}
.
- Deploy the application using the App deployment on macOS guidelines.
- Go to Desktop and create a new folder entitled
${ExampleProject}Installer
. - Here, create two subfolders entitled
config
andpackages
. - Within
config
create aconfig.xml
. - Within
packages
create a new subfolder, entitled:${ExampleProject}
. Here, create two further subfolders,data
andmeta
. data
folder contains all files to be installed, e.g.${ExampleProject}.dmg
or entirely thedeploy
folder, configuration files, logos, etc. Do not put here the source code if you do not want to provide it. As golden rule, add all data to be installed within a subfolder ofdata
namedmacOS
.meta
folder contains scripts and files for generating the installer with its GUI. Add here also additional files, such as the license to be accepted.
All componetes are now ready and it is time to create the installer file. To this aim:
- Open a terminal shell
- Go to
${ExampleProject}Installer
folder, i.e. whereconfig
andpackages
have been created:
cd ${path_to_${ExampleProject}Installer}
- Launch
QtInstallerFramework
:
~/Applications/Qt/Tools/QtInstallerFramework/${QtInstallerFramework_version}/clang_64/bin/binarycreator -c config/config.xml -p packages ${ExampleProject}Installer
- At the end of the project,
${ExampleProject}Installer.exe
will appear in${path_to_${ExampleProject}Installer}
.