Open ghost opened 4 years ago
Hmm... I know that internally an AppImage mounts a drive somewhere in /tmp. If you know where to look, do you mind seeing if manually setting the renderer works?
do you mind seeing if manually setting the renderer works?
I already tried, but it not solve issue:
AppImage on each launch mount content in dynamically generated folder named randomly on on each launch, for example: /tmp/.mount_thefraUq10gK/opt/theframe-render/bin/theframe-render
@vicr123, seems like continuous
AppImage builds failed with latest commits:
Check the GitHub Actions page for the latest builds. Sometimes it fails to release correctly.
https://github.com/vicr123/theFrame/actions/runs/152648485 for this case.
Check the GitHub Actions page for the latest builds.
Just tried, but theFrame still can't recognize bundled theframe-render
.
And even more, theFrame not parse path to theframe-render
file when trying manually select it from AppImage mounted folder.
Ahh that's a bit annoying, I'll continue debugging and let you know if I end up figuring it out. I have a feeling it may have to do with mixing host libraries maybe? :/
maybe? :/
As I proposed earlier, ask for help:
1.0
(AppImage)Actual behavior
Trying to render I reached "Renderer is unavailable!" warning and I could not render nothing.
If extract AppImage content via command
$ ./theframe-linux.AppImage --appimage-extract
I could see that there is some file:../squashfs-root/opt/theframe-render/bin/theframe-render
.Seems like
theframe-render
bundled into AppImage, but internally it not linked by relative path.Expected behavior
Link
thefram-render
inside AppImage so theFrame would recognize & use it.For any AppImage packaging questions & support: