Deployment / Build for Linux
Last updated
Last updated
From terminal from root of app, run the deployment script
Then
It creates a cache
and a build
folder. cache
is a folder used by deploy to keep the latest version needed to build and package the app, to avoid having to re-download it every time. While the packaged app ready for use can be found in the build
folder.
It packages the app as a AppImages
that works across linux distribution see deployment section and this issue and corresponding PR for more details.
Download an application, make it executable, and run! No need to install. No system libraries or system preferences are altered.
Distribute your desktop Linux application in the AppImage format and win users running all common Linux distributions. Package once and run everywhere. Reach users on all major desktop distributions.
Fore more details on how to run in Linux after download this see below
AppImages can be downloaded and run without installation or the need for root rights.
Making it executable You can make the appImage executable as follows:
chmod a+x exampleName.AppImage Executing it You can execute an appImage as follows:
./exampleName.AppImage
AppImages can be downloaded and run without installation or the need for root rights.
You can make the appImage executable as follows:
chmod a+x
exampleName.AppImage
Or see also how to make an AppImage executable for easier users instructions using GUI
You can execute an appImage as follows:
./exampleName.AppImage
Providing an AppImage would have, among others, these advantages:
Applications packaged as an AppImage can run on many distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)
One app = one file = super simple for users: just download one AppImage file, make it executable, and run
No unpacking or installation necessary
No root needed
No system libraries changed
Works out of the box, no installation of runtimes needed
Optional desktop integration with appimaged
Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
Can optionally GPG2-sign your AppImages (inside the file)
Works on Live ISOs
Can use the same AppImages when dual-booting multiple distributions
Can be listed in the AppImageHub central directory of available AppImages
Can double as a self-extracting compressed archive with the --appimage-extract
parameter
Here is an overview of projects that are already distributing upstream-provided, official AppImages.
If you have questions, AppImage developers are on #AppImage on irc.freenode.net.