If anyone's interested, you can find SMPlayer-'portable' at the following link:-Īny issues, etc, drop me a line. It may run in others, too won't hurt nothing to try. So far, this has been tested, and found to work in, Fossapup64, Bionicpup64, and Xenialpup64. The 'MenuReadMe' explains how to use these. Scripts are included, as usual, to permit adding a Menu entry if one is required, firing it up from wherever it's located. The sym-links are then removed again at close.Īs always, d/l unzip put it wherever you like.preferably outside the 'save'. I then built a 'portable' version of SMPlayer 21.8.0 in my now 'standard' layout this keeps the config stuff within its own directory, sym-linking it out to the expected locations at run-time. Having done that, I re-built the AppImage by the use of Fred's scripts. No 'static' compiling here, I'm sorry to say my own compiling is abysmal, never mind the fancy stuff! ) (I'm afraid this isn't as small as manages to craft them. These are definitely needed, since even Fossapup64 only has Qt 5.12 as standard.and Qt5-powered apps are way fussier about exact versions than Qt4-powered ones ever were.

Thus, I've removed more than 200 MB of extraneous items - unpacked in /tmp, the AppImage is almost 350 MB in size! - and pretty much just left the Qt 5.14 items that it needs to run, indicating the need to use these by means of an 'LD_LIBRARY_PATH' clause in the 'LAUNCH' script.

Turns out it comes with an awful lot of redundant dependencies & stuff, in the /lib directory, that most 64-bit Puppies have built-in already.

So I stripped the AppImage down via use of the '-appimage-extract' argument, and did some investigating. I thought I'd take a closer look at it, and see why it WAS so big. Having read peppyy's post, earlier this evening, about the SMPlayer v21.8.0 AppImage he found over at Sourceforge:.

Sm player portable