Oh excellent, thanks @slaeshjag it's a Debian Wheezy VM. @TrashyMG only the libgtk-3-dev, I'll try another version as well, if not then I'll comment them out. re: A15 not sure anything will be suitable really this is an vexpress-a9 machine, just haven't figured out the kernel recompile for vexpress-a15 yet (likely not for a while either).
I got bit further on by commenting out only to throw another load of syntax errors, so probably Wheezy is a dead end for any pyra related fun. Nevermind, back to researching a15 VM's, thanks.
I've used it on amd64, and there is enough of a mechanism to differentiate different architectures, their runtime environments, and what architecture the current install is capable of running.
Well, at the core of it all it really needs is a label to identify its intended architecture, and then the pnd runner can do a context switch to 32-bit mode to run it (assuming we're running a 64-bit OS) if it's not a 64-bit ARM package, or maybe lanuch QEMU on it if it's a completely foreign architecture. All that's really needed right now it the tag to identify its ABI, and it sounds like it's already got that and more, so that's good then.
Well it would be sleashjag, The code is a bit old, but I haven't had too much issues with it... I'm also using the factory installed Linux kernel and know there are some AUFS dependencies that would likely break if not using the specially compiled kernel aTc puts out.
Well AUFS can be enabled in the kernel easy enough aTc has experience with doing so.
This looks promising, but I know AUFS was used over other things was it could handle spanning different filesystems better than most... but not that familiar with this.
Believe this lacks two key features needed for DBPs, one DwarFS creates a readonly filesystem and we need to have a writable filesystem, and it doesn't mention any ability of creating unions which allows DBP root and appdata directory to merge over a local mount.
SquashFS is also read-only - and it should be like that. That's the whole point of the mentioned union in the first place. Writes to the mounted app directory should not alter the app itself.
And i think the union is a feature of the kernel, not of SquashFS itself.
DwarFS sounds good and sounds like a better choice than SquashFS if someone would attempt a redo (Sadly, nowadays thats a big if). But if it will improve performance of running games on Pandora or Pyra in reality is a different thing.
The dwarfs manual page also shows an example for setting up DwarFS with overlayfs in order to create a writable file system mount on top a read-only DwarFS image.
AppImage lacks dynamic/automatically loading and it's clunky to add custom files/ROMS etc to the appdata directory...
@Nilsnsn & @Magic Sam
From my understanding the issue isn't really squashfs with DBPs, you don't really need a squashfs image to make a DBP file from slaeshjag's original post. I think all the issues that arise from the DBP system and further maintainability is that it currently requires AUFS and needs to be manual enabled back into aTc's kernel builds.
Actually there is a daemon that adds AppImages to your start menu.
I do not really see the need for an appdata folder any more.
For ROMS and files, they should not be in specific appdata folders anyways but on universal places where different emulators can access them.
It might be a different story for ports of commercial games that just contain the engine but need game files.
Would it not be possible for an AppImage to specify the location of those files relatively to the location of the AppImage?
Post automatically merged:
DBP has the huge disadvantage to (at least currently) not working on exFat drives which is what large SD cards use.
Because of that issue I wanted to place one in my home folder just for testing.
Did not work, because the DBP needed to create an appdata folder in my root directory where it had no permission for.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.