
The application will run, but the functionality will be disabled due to the missing plugins. As we cannot deploy plugins using the static linking approach, the bundle we have prepared so far is incomplete. The Plug & Paint example consists of several components: The core application ( Plug & Paint), and the Basic Tools and Extra Filters plugins. or edit the Makefile and replace link lines for the Qt libraries with the absolute path to the static libraries.dylibs) away to another directory while you link the application and then move them back, If you want to use only static libraries, you can either: The linker always chooses dynamic linking over static. If you see Qt libraries in the output, it probably means that you have both dynamic and static Qt libraries installed on your machine. (compatibility version 1.0.0, current version 88.0.0) (compatibility version 1.0.0, current version 92.0.0) (compatibility version 1.0.0, current version 1.0.0) (compatibility version 7.0.0, current version 7.3.0) (compatibility version 1.0.0, current version 22.0.0) framework /Versions /A /ApplicationServices

System /Library /Frameworks /ApplicationServices. (compatibility version 1.0.0, current version 1.2.3) (compatibility version 1.0.0, current version 10.0.0) (compatibility version 2.0.0, current version 128.0.0) To disable this, add the following statement to your application's project file (. Qmake automatically generates a bundle for your application.

For more information about bundles, see Apple's Developer Website. This is specific to macOS and beyond the scope of this document.
QT FOR MAC OS X HOW TO
This document describes how to create a macOS bundle and make sure that the application finds the resources it needs at run-time.
