Appimage: Difference between revisions
m attached to category:software |
mention binfmt option (adapted from old wiki) |
||
Line 14: | Line 14: | ||
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=" | Since [https://nixos.org/manual/nixos/stable/release-notes#sec-release-24.05-new-services NixOS 24.05], there is a binfmt option: | ||
<syntaxhighlight lang="nixos"> | |||
programs.appimage.binfmt = true; | |||
</syntaxhighlight> | </syntaxhighlight> | ||
This way AppImage files can be invoked directly | This way AppImage files can be invoked directly as if they were normal programs | ||
== How AppImage files are packaged by NixOS == | == How AppImage files are packaged by NixOS == |