Package Details: ppsspp-git 1.17.1.r785.cbdb2a37eb-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.163039
First Submitted: 2012-11-05 20:36 (UTC)
Last Updated: 2024-06-21 11:26 (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 .. 14 Next › Last »

Shatur commented on 2023-07-06 08:48 (UTC)

@loathingkernel the script has been upstreamed: https://github.com/hrydgard/ppsspp-ffmpeg/commit/a94f3e6fa89e6ac5763e6b9d23ab3c4a72bbcd6c

loathingkernel commented on 2023-06-30 09:34 (UTC) (edited on 2023-06-30 09:38 (UTC) by loathingkernel)

@Shatur if you can write a proper patch that handles selecting the correct script and incorporates cleanly with the PKGBUILD, I can merge it.

On the other hand, if the upstream script is for cross-compiling, you should first merge the native aarch64 build script upstream and then adapt the PKGBUILD. I don't want to carry custom scripts with the PKGBUILD, as it is outside the scope, especially since aarch64 is not officially supported by Arch itself.

Shatur commented on 2023-06-28 09:04 (UTC) (edited on 2023-06-28 10:18 (UTC) by Shatur)

Could you add support for aarch64? The only change is to to run the correct ffmpeg script depending on the arch. Here is for aarch64 (the default one is for cross-compilation)

kylon commented on 2023-04-20 10:47 (UTC)

to build until updated, patch

--- PKGBUILD    2023-02-06 04:12:46.000000000 +0100
+++ ppsspp-git/PKGBUILD 2023-04-20 12:44:59.503456449 +0200
@@ -41,7 +41,7 @@
   git+https://github.com/Kingcom/armips.git
   git+https://github.com/discordapp/discord-rpc.git
   ppsspp-ffmpeg::git+https://github.com/hrydgard/ppsspp-ffmpeg.git
-  ppsspp-glslang::git+https://github.com/hrydgard/glslang.git
+  git+https://github.com/KhronosGroup/glslang.git
   git+https://github.com/hrydgard/ppsspp-lang.git
   git+https://github.com/Tencent/rapidjson.git
   git+https://github.com/KhronosGroup/SPIRV-Cross.git
@@ -74,12 +74,12 @@
 prepare() {
   cd ppsspp

-  for submodule in assets/lang ext/glslang ffmpeg; do
+  for submodule in assets/lang ffmpeg; do
     git submodule init ${submodule}
     git config submodule.${submodule}.url ../ppsspp-${submodule#*/}
     git -c protocol.file.allow=always submodule update ${submodule}
   done
-  for submodule in ext/{armips,discord-rpc,rapidjson,SPIRV-Cross,zstd,cpu_features}; do
+  for submodule in ext/{glslang,armips,discord-rpc,rapidjson,SPIRV-Cross,zstd,cpu_features}; do
     git submodule init ${submodule}
     git config submodule.${submodule}.url ../${submodule#*/}
     git -c protocol.file.allow=always submodule update ${submodule}

zxcv commented on 2023-04-05 23:48 (UTC) (edited on 2023-04-05 23:50 (UTC) by zxcv)

There is some problem with submodule download during prepare:

Submodule 'ext/glslang' (https://github.com/KhronosGroup/glslang.git) registered for path 'ext/glslang'
Cloning into '/home/user/.cache/yay/ppsspp-git/src/ppsspp/ext/glslang'...
done.
fatal: git upload-pack: not our ref b34f619e1c85810dcb3c578107d2e48ba4ee2b37
fatal: remote error: upload-pack: not our ref b34f619e1c85810dcb3c578107d2e48ba4ee2b37
fatal: Fetched in submodule path 'ext/glslang', but it did not contain b34f619e1c85810dcb3c578107d2e48ba4ee2b37. Direct fetching of that commit failed.

E3LDDfrK commented on 2022-08-02 16:27 (UTC) (edited on 2022-08-02 16:34 (UTC) by E3LDDfrK)

edit: Never mind. It seems it's just that it needs to download a lot of things. And my aur helper doesn't show it individually. Doing it manually with makepkg shows it takes a while to download everything.

Personally I'm stuck at this step:

:: Downloading the latest sources for devel packages ppsspp-qt-git, ppsspp-common-git...

Not exactly sure why.

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.

xdavidwu commented on 2020-12-17 06:04 (UTC) (edited on 2021-10-01 07:06 (UTC) by xdavidwu)

@kage52124 The idea is that keeping them together in a PKGBUILD makes them stay at same version naturally. The subpackage ppsspp-common-git is needed by all variants and ideally needs to be from the same source version as those variants. Keeping them in a single PKGBUILD prevents version mismatch. I think it would not be reliable if we seperate them into individual PKGBUILDs and have dependencies with version locked as there is no way to be sure that the sources downloaded would be at exactly the same version when building them seperately.

You can always edit PKGBUILD before building to prevent builds that you don't need. If you need prebuilt packages, I also provide them at https://aurbuild.xdavidwu.link/ (daily builds) signed with key F73F137D4573DEFAA097DBF09544CFF6B08A3FD3.

kage52124 commented on 2020-12-16 22:35 (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.

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