Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update appimagetool link #5721

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

Drsheppard01
Copy link

It helps to build AppImage for any linux include musl-based
This pr also raises the question of the need for additional builds for ubuntu, ubuntu-latest and fedora

It helps to build AppImage for any linux include musl-based
This pr also raises the question of the need for additional builds for ubuntu, ubuntu-latest and fedora
@lanewei120 lanewei120 requested a review from MackBambu January 9, 2025 11:35
@MackBambu MackBambu self-assigned this Jan 9, 2025
@MackBambu
Copy link
Contributor

This does not appear to be a stable version. What issues might be resolved by using this version of the AppImage build tool?

@Drsheppard01
Copy link
Author

Firstly, this solves the libfuse problem, (on ubuntu only fuse3 is shipped by default, while the appimage kpc only work with version 2)
Secondly, it will potentially make it work for systems on musl libc, but that's not certain

@Samueru-sama
Copy link

This does not appear to be a stable version. What issues might be resolved by using this version of the AppImage build tool?

Hi, that appimagetool is stable and uses the static appimage runtime from here.

This removes the libfuse2 dependency from the AppImage, which is an EOL library that no longer comes on new distros by default.


Since the runtime is static is also allows to make AppImages that work on any linux system, like this one.

I noticed right now you have 3 different appimage releases, likely due to the webkit2gtk incompatibility issue, the only way to fix that issue is to bundle webkit2gtk in the AppImage along with opengl since the lib needs a specific version of opengl to work otherwise you will have a different white screen issue.

@MackBambu
Copy link
Contributor

@Drsheppard01 Thank you for your submission. I will will more tests on the new packaging tool.

I noticed right now you have 3 different appimage releases, likely due to the webkit2gtk incompatibility issue, the only way to fix that issue is to bundle webkit2gtk in the AppImage along with opengl since the lib needs a specific version of opengl to work otherwise you will have a different white screen issue.

@Samueru-sama
Is there a similar project that packages webkit2gtk and OpenGL for reference? I've been stuck on this for a long time.

@Samueru-sama
Copy link

Samueru-sama commented Jan 24, 2025

Is there a similar project that packages webkit2gtk and OpenGL for reference? I've been stuck on this for a long time.

The very AppImage of PrusaSlicer that probonopd made that I just linked in the original comment xd

steps

Note that the tool that's being used, which is sharun recently got something called hooks that do a lot of those steps automatically, I made the PR to add the webkit2gtk hook to avoid doing that was done originally with the Prusa appimage of doing it all manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants