You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
probonopd b3b5010ec1 Go back to objdump for now; remove sections concerning macOS Frameworks 8 years ago
linuxdeployqt Rename to linuxdeployqt 8 years ago
shared Go back to objdump for now; remove sections concerning macOS Frameworks 8 years ago
.gitignore Initial commit 8 years ago
README.md Update README.md 8 years ago
linuxdeployqt.pro Rename to linuxdeployqt 8 years ago

README.md

linuxdeployqt

linuxdeployqt takes an application as input and makes it self-contained by copying in the Qt libraries and plugins that the application uses. It is based on macdeployqt in the tools applications of the Qt Toolkit.

Known issues

  • This is not fully working yet. This is not ready for production use. Help is appreciated.
  • Some functions still refer to macOS specifics. These need to be converted over to their Linux counterparts or deleted.

Installation

  • Open in Qt Creator and build
  • Build and install patchelf (a small utility to modify the dynamic linker and RPATH of ELF executables; similar to install_name_tool on macOS)

Usage

Usage: linuxdeployqt app-binary [options]

Options:
   -verbose=<0-3>     : 0 = no output, 1 = error/warning (default), 2 = normal, 3 = debug
   -no-plugins        : Skip plugin deployment
   -appimage          : Create an AppImage
   -no-strip          : Don't run 'strip' on the binaries
   -use-debug-libs    : Deploy with debug versions of frameworks and plugins (implies -no-strip)
   -executable=<path> : Let the given executable use the deployed frameworks too
   -qmldir=<path>     : Scan for QML imports in the given path
   -always-overwrite  : Copy files even if the target file exists
   -libpath=<path>    : Add the given path to the library search path

linuxdeployqt takes an application as input and makes it
self-contained by copying in the Qt libraries and plugins that
the application uses.