Package Details: ppsspp-git 1.18.1.r1606.f573b0c72c-1

Git Clone URL: https://aur.archlinux.org/ppsspp-git.git (read-only, click to copy)
Package Base: ppsspp-git
Description: A PSP emulator written in C++
Upstream URL: https://www.ppsspp.org/
Licenses: GPL2
Conflicts: ppsspp
Provides: ppsspp
Submitter: libcg
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 43
Popularity: 0.015664
First Submitted: 2012-11-05 20:36 (UTC)
Last Updated: 2025-04-06 14:33 (UTC)

Pinned Comments

xdavidwu commented on 2021-02-09 03:30 (UTC)

Please don't flag this package out-of-date when you see the version string is. This is a VCS package. It always grabs the latest source from upstream repo and version string is generated at build time. As long as it builds fine, it is up-to-date. It is your responsibility to decide when to rebuild (update). I won't bump the version for you.

Also, I am running a daily build service, and by that, I can check that it builds fine daily. Ancient version string does not mean that I have loose track of the latest source.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 14 Next › Last »

Griever commented on 2018-06-18 02:48 (UTC) (edited on 2018-06-18 18:37 (UTC) by Griever)

Similar to @loathingkernel, wouldn't it be better to build ffmpeg instead of relying on prebuilts? It would reduce the checkout time and save bandwidth. Compilation time is very short due to the buildscript only enabling the bare minimum features required for emulation.

As far as I know, PPSSPP's ffmpeg repo differences from upstream are only including prebuilt binaries and buildscripts, no actual source changes.

Also similar to @loathingkernel, I created a PKGBUILD1 which uses ffmpeg 3.0.x but instead of using an official release archive, I just use a snapshot of the 3.0.x branch. You could modify the .gitmodules file to use ffmpeg's git repo and set the branch but the checkout time and size is rather large due to the number of commits. AFAIK, you can't git submodule update a shallow clone of a branch.

Might I also suggest replacing PPSSPP's SDL gamecontrollerdb.txt with https://github.com/gabomdq/SDL_GameControllerDB? It has much better out-of-box controller support.

1: Please excuse the removal of maintainers/contrib in the pkgbuild; the repo is for personal use and I remove them and replace with a dummy maintainer to improve readability and appease linters.

Enverex commented on 2018-05-26 19:29 (UTC)

This package refuses to install anymore as it seems to conflict with itself:

:: ppsspp-git and ppsspp-qt-git are in conflict

It's a multi-package PKGBUILD which makes ppsspp-git, ppsspp-headless-git, ppsspp-qt-git, so when it tries to install all 3 of them, it fails.

loathingkernel commented on 2018-01-17 17:18 (UTC) (edited on 2018-01-17 17:56 (UTC) by loathingkernel)

I have a suggestion. Instead of pulling in ppsspp-ffmpeg repository, which is almost 1gb of binaries, ppsspp can be built using the latest ffmpeg from the 3.0.x branch. This also takes advantage of any bug fixes in ffmpeg as the version in the repository is stuck at 3.0.2. Thankfully upstream provides a script to statically build the minimal ffmpeg they need.

Here is my take on the PKGBUILD if you are interested https://gist.github.com/loathingKernel/4dcd7a56a56c1a56b3622e587ef7badf

Ignore the clang stuff or the lack of -git suffix, it is just my personal preference.

alucryd commented on 2017-05-19 23:47 (UTC)

The wrappers should now handle evil spaces. As for why they're there, it appears there were issues when assets were in /usr/share/ppsspp, also, with all due respect to upstream, I don't want the main binaries to have ugly all caps names, the main binary should be named after the package.

Enverex commented on 2017-05-17 12:37 (UTC)

There's a few issues with this at the moment. The wrapper script doesn't handle variables very well and breaks paths that contain spaces (you can't escape them either with slashes or quotes) so that needs to be changed. e.g. "ppsspp /path/to\ my/file\ is\ here.iso" won't work. That said, the wrapper itself may not be necessary at all anymore as PPSSPP supports installing the assets folder system-wide (as of https://github.com/hrydgard/ppsspp/pull/6692) therefore PPSSPP can now be installed to /usr/bin and the assets to /usr/bin/ppsspp/assets, negating the need for the wrapper scripts at all.

alucryd commented on 2017-04-11 20:50 (UTC)

Should be all good now, I'll do the same with the community package sometime this week.

mac1202 commented on 2017-04-11 18:14 (UTC)

Can you take a look at this https://github.com/hrydgard/ppsspp/issues/9564. thanks.

alucryd commented on 2017-04-05 21:36 (UTC)

Don't you worry about that, I just didn't realized ppsspp handled FHS that badly... Fixed both here and in [community], even threw the headless version in for the same price.

loathingkernel commented on 2017-04-05 11:23 (UTC) (edited on 2017-04-05 15:12 (UTC) by loathingkernel)

Are you sure you can manage alone? Because ppsspp-qt still doesn't run, as it complains about missing assets in the executable directory (I don't mean that you should put them in /usr/bin but it is something the packaging should take care of) and ppssppsdl still has unresonably high CPU usage in the menu due to renaming the executable. These issues exist in the official repo packages too.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 14 Next › Last »