1
0
mirror of synced 2024-12-02 19:27:21 +01:00
ImHex/dist/AppImage
wardwouts 451c550b19
build: Simplify appimage build (#356)
* Simplify creating an AppImage

- package.sh packages the build result into an AppImage. It requires
squashfs-tools to work
- runtime-x86_64 is a binary distributed by the AppImage project that takes
care of extracting and running the image

* use AppRun from AppImage project

* clean up no longer needed bits

* Keep docker way of working around

- Docker now also uses `package.sh`, so no more need for FUSE.
- Fetch binaries instead of storing in git.

* Fix details

* wait a little longer for the container to start
2021-12-03 09:53:15 +01:00
..
build.sh build: Simplify appimage build (#356) 2021-12-03 09:53:15 +01:00
Dockerfile build: Simplify appimage build (#356) 2021-12-03 09:53:15 +01:00
extract.sh build: Simplify appimage build (#356) 2021-12-03 09:53:15 +01:00
ImHex.desktop build: Added AppImage builder (#355) 2021-12-01 21:35:47 +01:00
imhex.png build: Added AppImage builder (#355) 2021-12-01 21:35:47 +01:00
package.sh build: Simplify appimage build (#356) 2021-12-03 09:53:15 +01:00
README.md build: Simplify appimage build (#356) 2021-12-03 09:53:15 +01:00

Building an AppImage

There are two ways of building an AppImage for ImHex, using the provided tools here.

If you want to create an AppImage and do not have a build to work from already, you can use docker to build ImHex and package an AppImage.

Alternatively you can create an AppImage using an existing build.

Using docker

First run build.sh to create a docker image. Then run extract.sh to get the AppImage out. This needs to be in two steps, as a docker build cannot copy files out. Nor can docker build use volume mounts.

The environment variable TAG can be set to build for a specific git tag. Without the master branch is build.

Using an existing build

Run package.sh with the build dir as an argument. E.g.:

./package.sh ../../build