Overview of Qt Installer Framework | Qt Installer Framework Documentation 4.10.0

- Qt Installer Framework Documentation
- Overview of Qt Installer Framework
- Qt Installer Framework 4.10.0

Getting Started ◦ Installation

# Overview of Qt Installer Framework

With Qt Installer Framework you can create both simple and complex installers with thousands of components and deploy your installers across all the supported desktop Qt platforms without rewriting the source code. Your final installers have the native look and feel of the platform on which they run: Linux, Microsoft Windows, and macOS.

For example Qt installers are made with the Qt Installer Framework.

Both open-source and commercial users can download Qt Installer Framework from their Qt Account.

Qt Installer Framework tools generate installers with a set of pages that guide the users during the installation, update, or uninstallation process. You supply the installable content and specify information about it, such as the name of the product and the installer and the text for the license agreement.

You can customize the installers by adding widgets to the predefined pages or by adding whole pages to offer users more options.

Each installable package in the installer can contain one component script that gives a comprehensive API to fine-tune how the package should be installed on the system. You can, for example, add shortcuts to the desktop or register file extensions for your tool.

## Choosing Installer Type

You can offer end users an offline or online installer, or both, depending on your use cases.

Both installers install a maintenance tool, which allows your end users to later add, update, and remove components. End users can use the maintenance tool to install more components from the server after the initial installation, as well as to receive automatic updates to content as soon as the updates are available on the server. However, this works for an offline installation only if you specify a repository address in the offline installer configuration or if end users specify the repository address themselves in the maintenance tool settings.

### Offline Installers

Offline installers contain all the installable components and do not require network connections during the installation.

Create an offline installer to enable users to directly download the installation package on a media for installation on a computer later. You can also distribute the installation package on a CD-ROM or USB stick, for example.

### Online installers

Online installers install the maintenance tool and components from an online repository on a web server. After installation, the maintenance tool can be used to modify the installation from an online repository.

The size of an online installer binary is smaller and its download time is shorter than that of an offline installer binary. The total time spent downloading and running an online installer might also be shorter than downloading and running an offline installer if the end users do not install all the available components.

Create an online installer to enable users to always install the latest versions of the content packages.

- Online repositories
- Online installer

### Signing installers

Signing your installer is an integral step in finalizing your product. Signing shows that your code is safe and secure.

Find more information on signing your installer on Windows platform on Microsoft website. For more information on signing your installer in macOS, see Apple website for code signing and {https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution} {notarizing}.

## Promoting Updates for Online Installers

Make online repositories available to promote updates to end users who install your product. The easiest way to offer an update is to recreate the repository and upload it to the web server. For large repositories, you can update only the changed components.

## Providing Content for Installers

You can enable other content providers to add components to the installer as add-on components. The component providers must set up repositories that contain the installable components and deliver the URL that points to the repositories to end users. End users must then configure the URL in the installer. The add-on components are visible in the package manager.

Getting Started ◦ Installation