| 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) |
Question: It looks like this PKGBUILD is building all of the versions of PPSSPP, but only installing one of them, based on what I see as it compiles. Is that right? If so, would it not make more sense to drop the build instructions for QT and Headless, leaving those for other packages?
The install worked great, btw, but compiling on an old, fanless, Celeron takes time.
I have solved all depenencies (submodules or packages) problems. Also, some changes have been made to make this pkgbase better:
Instead of /opt, it now installs to /usr like ppsspp in [community] does. Wrappers have been removed and binaries are now in /usr/bin as PPSSPP{SDL,Headless,Qt}.
A new subpackage, ppsspp-common-git, has been introduced. Shared assets are moved there. This solves inner conflicts of subpackages.
I'm receiving the following error during build:
...
CMake Error: File /home/drb/.cache/yay/ppsspp-git/src/ppsspp/ext/miniupnp/miniupnpc/miniupnpcstrings.h.cmake does not exist.
CMake Error at CMakeLists.txt:1865 (configure_file):
configure_file Problem configuring file
...
==> ERROR: A failure occurred in build().
Aborting...
The following patch fixes the build:
diff --git a/PKGBUILD b/PKGBUILD
index b901a0b..4aa37d7 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -11,7 +11,7 @@ pkgname=(
ppsspp-headless-git
ppsspp-qt-git
)
-pkgver=1.8.0.r358.2a664add3
+pkgver=1.10.3.r413.a5b6f8cb0
pkgrel=1
pkgdesc='A PSP emulator written in C++'
arch=(x86_64)
@@ -44,6 +44,7 @@ source=(
git+https://github.com/Tencent/rapidjson.git
git+https://github.com/KhronosGroup/SPIRV-Cross.git
armips-tinyformat::git+https://github.com/Kingcom/tinyformat.git
+ git+https://github.com/hrydgard/miniupnp.git
ppsspp.sh
ppsspp-headless.sh
ppsspp-qt.sh
@@ -60,6 +61,7 @@ sha256sums=('SKIP'
'SKIP'
'SKIP'
'SKIP'
+ 'SKIP'
'2c2d1ee6d1ce5c2acec372d58b8079885f6d5d674633cfea489cd550252a5426'
'1236ce000bb670ee2c0e0645c3d55f4d8c8e74dbc35a1af0962a3bdd7608f1c5'
'828b06aacc56672a4d953d77342717c5be414a68261025f74e466abd084b8e6b'
@@ -83,7 +85,7 @@ prepare() {
git config submodule.${submodule}.url ../ppsspp-${submodule#*/}
git submodule update ${submodule}
done
- for submodule in ext/{armips,discord-rpc,rapidjson,SPIRV-Cross}; do
+ for submodule in ext/{armips,discord-rpc,rapidjson,SPIRV-Cross,miniupnp}; do
git submodule init ${submodule}
git config submodule.${submodule}.url ../${submodule#*/}
git submodule update ${submodule}
Introduced by commit eb7b6b38f6ce5e25ec4972a2415a91ba82fb3389
Indeed, they've added 2 new submodules. Forgot to add ppsspp-git back to my automated builds so I didn't catch that change. Just pushed an updated PKGBUILD, thanks for the heads up.
Thanks alucryd. I hadn't ran into that myself.
I think one of the recent GIT updates may have broken the package. Not sure if it can be fixed in the build script or if it's simply a case of waiting for upstream to fix something. It fails immediately after configuring with:
CMake Error at ext/discord-rpc-build/CMakeLists.txt:33 (add_library): Cannot find source file: ../discord-rpc/src/backoff.h
Yes, system ffmpeg doesn't work. Try running the first patapon for example, don't remember what the exact symptoms, but there are issues with the intro video for instance.
Is there any reason at this point to build FFMPEG along with this package rather than using the system version of FFMPEG? (via the build flag -DUSE_SYSTEM_FFMPEG). I haven't noticed any issues with this and it cuts down repo sync / compile time significantly.
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.