There shouldn’t be a problem on the computer but there may be some flag for the architecture you are targeting so use there armv8
The other one is a library that maybe the appimage will look into the /usr so it has to be installed in some way.
This means that it would be better to start by creating snaps and then move to appimages.
There is a developer mode that may mount the entire system as writable. I will look at this!
I put a screenshot here:
Building snaps with snapcraft, How to create a Snap package step by step in Linux , Craft a snap - Snapcraft 8.14.0 documentation
Maybe your home directory is already in the command path variable (environment variable), this means that the executables and links in home can be executed from any location.
printenv
If not you can add it or any other directory as a command path so that you don’t write in the file system but to add it should demand root privileges again.
This looks good! I will look into these things. It has written snaps in the root directory so they have permission that I don’t!
So everything you throw into /home/phablet/.local/bin will be executable from every location, throw in there the busybox symbolic links for your commands and any other executable.
Ok-in addition to the busybox symbolic link I will put the executable in there from SMPlayer.
