сб, 19 окт. 2024 г., 21:33 Andrew Randrianasulu <[email protected]>:

https://github.com/AppImage/type2-runtime/issues/77

I think I fixed it, now it builds inside Alpine chroot and correctly copied out before chroot deleted (debuggin this was ... slow)

I see it uses libfuse3 so hopefully there will be no need for libfuse2 workaround on new Debian 11, etc.

But I have not tried to use this runtime part anywhere yet.

Build takes around 400 mb in /tmp

So, it seems to work? I downloaded https://github.com/AppImage/appimagetool with git clone (commit 81ee1db4946780292cd046d4c269a9b4fd7bc29d ) cd appimagetiool mkdir build cd build cmake .. make now executable in src, relative to current dir used it with just-built runtime: ./src/appimagetool /dev/shm/new-git/cinelerra/cinelerra-5.1/AppDir/ --runtime-file /root/src/type2-runtime/out/runtime-i686 AppDir was generated earlier by appimage-building script. now file states that new appimage is cin-i686.AppImage: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped as opposed to another one built earlier file /dev/shm/new-git/cinelerra/cinelerra-5.1/cin-i386.AppImage /dev/shm/new-git/cinelerra/cinelerra-5.1/cin-i386.AppImage: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=3570a458670210b103da45068d2dcd220f17e497, stripped so, in theory it should be more compatible? but it uses by default slower compression, zstd (hopefully you can change that)