Appimage/en: Difference between revisions
Updating to match new version of source page |
Updating to match new version of source page Tags: Mobile edit Mobile web edit |
||
(2 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
=== Packaging === | === Packaging === | ||
See the [https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-appimageTools nixpkgs manual on wrapping AppImage packages]. In short, the AppImage is extracted and any dependencies are added as | See the [https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-appimageTools nixpkgs manual on wrapping AppImage packages]. In short, the AppImage is extracted and any dependencies are added as Nix build dependencies. | ||
Following example is a derivation for the program Quba, which is also distributed as AppImage.<syntaxhighlight lang="nix"> | Following example is a derivation for the program Quba, which is also distributed as AppImage. | ||
<syntaxhighlight lang="nix"> | |||
{ | { | ||
lib, | lib, | ||
Line 25: | Line 27: | ||
version = "1.4.0"; | version = "1.4.0"; | ||
pname = "quba"; | pname = "quba"; | ||
src = fetchurl { | src = fetchurl { | ||
Line 34: | Line 35: | ||
appimageContents = appimageTools.extractType1 { inherit name src; }; | appimageContents = appimageTools.extractType1 { inherit name src; }; | ||
in | in | ||
appimageTools. | appimageTools.wrapType2 rec { | ||
inherit | inherit pname version src; | ||
extraInstallCommands = '' | extraInstallCommands = '' | ||
substituteInPlace $out/share/applications/${pname}.desktop \ | substituteInPlace $out/share/applications/${pname}.desktop \ | ||
--replace-fail 'Exec=AppRun' 'Exec=${ | --replace-fail 'Exec=AppRun' 'Exec=${meta.mainProgram}' | ||
''; | ''; | ||
Line 56: | Line 54: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
== Configuration == | == Configuration == | ||
Line 61: | Line 60: | ||
=== Register AppImage files as a binary type to binfmt_misc === | === Register AppImage files as a binary type to binfmt_misc === | ||
You can tell the Linux kernel to use an interpreter (e.g. <code>appimage-run</code>) when executing certain binary files through the use of [https://en.wikipedia.org/wiki/Binfmt_misc#External_links binfmt_misc], either by filename extension or magic number matching. Below NixOS configuration registers AppImage files (ELF files with magic number "AI" + 0x02) to be run with <code>appimage-run</code> as interpreter | You can tell the [[Linux kernel]] to use an interpreter (e.g. <code>appimage-run</code>) when executing certain binary files through the use of [https://en.wikipedia.org/wiki/Binfmt_misc#External_links binfmt_misc], either by filename extension or magic number matching. Below NixOS configuration registers AppImage files (ELF files with magic number "AI" + 0x02) to be run with <code>appimage-run</code> as interpreter: | ||
<syntaxhighlight lang="nixos"> | <syntaxhighlight lang="nixos"> | ||
programs.appimage = { | programs.appimage = { | ||
Line 74: | Line 70: | ||
This way AppImage files can be invoked directly as if they were normal programs | This way AppImage files can be invoked directly as if they were normal programs | ||
[[Category:Software | [[Category:Software]] |
Latest revision as of 17:17, 7 October 2025
AppImage is a monolithic packaging format for linux applications. It contains all dependencies in one file that is composed of an executable with a tacked on filesystem.
Usage
Run
On most distros, all one has to do is download the .AppImage
file, make it executable chmod +x $AppImage
, and execute it. This doesn't work in NixOS out of the box though, as AppImage files usually (if not always) depend on certain system libraries in hardcoded paths.
$ nix-shell -p appimage-run
$ appimage-run $AppImageFile
Packaging
See the nixpkgs manual on wrapping AppImage packages. In short, the AppImage is extracted and any dependencies are added as Nix build dependencies. Following example is a derivation for the program Quba, which is also distributed as AppImage.
{
lib,
appimageTools,
fetchurl,
}:
let
version = "1.4.0";
pname = "quba";
src = fetchurl {
url = "https://github.com/ZUGFeRD/quba-viewer/releases/download/v${version}/Quba-${version}.AppImage";
hash = "sha256-EsTF7W1np5qbQQh3pdqsFe32olvGK3AowGWjqHPEfoM=";
};
appimageContents = appimageTools.extractType1 { inherit name src; };
in
appimageTools.wrapType2 rec {
inherit pname version src;
extraInstallCommands = ''
substituteInPlace $out/share/applications/${pname}.desktop \
--replace-fail 'Exec=AppRun' 'Exec=${meta.mainProgram}'
'';
meta = {
description = "Viewer for electronic invoices";
homepage = "https://github.com/ZUGFeRD/quba-viewer";
downloadPage = "https://github.com/ZUGFeRD/quba-viewer/releases";
license = lib.licenses.asl20;
sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ];
maintainers = with lib.maintainers; [ onny ];
platforms = [ "x86_64-linux" ];
};
}
Configuration
Register AppImage files as a binary type to binfmt_misc
You can tell the Linux kernel to use an interpreter (e.g. appimage-run
) when executing certain binary files through the use of binfmt_misc, either by filename extension or magic number matching. Below NixOS configuration registers AppImage files (ELF files with magic number "AI" + 0x02) to be run with appimage-run
as interpreter:
programs.appimage = {
enable = true;
binfmt = true;
};
This way AppImage files can be invoked directly as if they were normal programs