Deploy and Run Applications on Qt Application Manager Devices
Overall, the deployment consists of four steps that depend on each other. Usually, you can use the default settings.
Warning: The deployment only works if you have added the
info.yaml file to your project file. When using qmake you can use the
OTHER_FILES variable. This
info.yaml file has to comply with the Qt Application Manager Manifest Definition.
The plugin takes the following deployment steps:
- Make install
The plugin automatically executes a
make installcommand to a temporary location within the build directory. You can add files to the package by using the INSTALLS variable.
Note: Your application needs to be self contained and ship all its dependencies within the application package (except for dependencies to the general system available on the target, like Qt or QML imports).
- Create Application Manager package
The packaging utility is used to create the package file based on the content available in the source directory. For more information, see Qt Application Manager packager.
- Deploy Application Manager package
In this step the plugin copies the package file to a temporary location on the target. For local PC this step is hidden.
- Install Application Manager package
The package file will be installed into the system using the controller utility on the target. For more information, see Qt Application Manager controller
appmanshall be running on the target or this step will fail.
Before the application is launched start the System UI on a target device. For more details, see Deploy and Run the System UI.
Available under certain Qt licenses.
Find out more.