tails_ wrote:Cool! May I now ask you for sources so I can compile this on my Debian-based phone? :P
P.S. How hard will it be to switch to libao instead of hardcoding support for PA or OSS?
Err, I got the source (and thus the link in the PKGBUILD) from
the OP of this very thread :D {edit: unless you meant source for the script etc. - you can get that from the tarball on the AUR page or from
my aurpkgs github repo} It shouldn't be too hard to build on other distros, as the required dependencies are minimal:
Code: Select all
$ ldd ./VGMPlay
linux-vdso.so.1 (0x00007fff00bff000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f8b82ebb000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f8b82bc1000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007f8b829b9000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f8b827a3000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f8b823fc000)
/lib/ld-linux-x86-64.so.2 (0x00007f8b830d7000)
I can't really help with libao as I'm no C programmer; I just did what I could with bash to fix possible issues in a packaged version (hence adding the config workaround and --help output and such). As far as audio, the program itself only outputs to OSS; ALSA has kernel modules that emulate OSS (hence me not mentioning them in the launcher), whereas pulse has the padsp script that is used if needed. Doing it all in a bash wrapper is indeed not ideal, but I'd personally rather show something that works rather than pleading to Valley Bell while showing no work :)
tails_ wrote:I just noticed that you described GPL license in PKGBUILD ...
As mentioned, it was a best-guess sort of thing - since I found nothing in VGMPlay itself I looked at the licenses of a bunch of the emulator cores mentioned in the readme. The least permissive of what I saw was Gens-GS's core: Gens-GS is under the GPL, which (as far as I understand) propagates to the standard VGMPlay build itself as long as that core is included. The other stuff I looked at was GPL-compatible so I went with it, but I can go through and add each individual license later ...
There's no overarching free/not-free restrictions in Arch as long as a work can be redistributed in repo form (especially in the AUR, which includes PKGBUILDs for things that specifically cannot be redistributed - they instead rely on you providing a copy of the data in question to construct the package. My own
fs2-open_data package is an example of such a construction), and I didn't see anything blocking any redistribution. If I missed something or completely misinterpreted the licensing, oops and mea culpa ._.
RichterEX2 wrote:Does this mean we're that much closer to something that'll work on Android OS? Because that would be rather neat.
I have no idea - there are a few "VGM" players on the Android market, but none that support everything this does. Kinda disappointing, really ...