qt5-base
and qt5-multimedia
should be removed from dependencies if possible.
edit: thanks
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.019231 |
First Submitted: | 2012-11-05 20:36 (UTC) |
Last Updated: | 2025-04-06 14:33 (UTC) |
qt5-base
and qt5-multimedia
should be removed from dependencies if possible.
edit: thanks
@kylon thanks for pointing me to that issue. I will consider it.
can we stop building qt variant since it is unmaintained, it lacks vulkan and recently it crashes a lot after recent qt updates? (see https://github.com/hrydgard/ppsspp/pull/19229 , qt should not be shipped)
it is just a waste of build time and cpu for no reason, also annoying to have 2 ppsspp in menu, just stick with officially supported and fully working sdl
This package doesn't build, aparently it needs the ext/OpenXR-SDK
submodule in the _ppsspp_submodules
@Technetium1 What? Why would it?
EDIT: Accidentally commented on the wrong package, sorry. Please disregard.
@loathingkernel no problem, here is a patch that compiles on my PinePhone: https://pastebin.com/ZizYLtN7. I did it before the skeleton commit, so I would suggest to revert the last commit and apply this instead.
@Shatur The reason I asked you to write a patch and send it is because I can't test the PKGBUILD on aarch64
. That being said, I have added the required skeleton in the PKGBUILD to support multiarch. I will be waiting for your patch.
@loathingkernel sorry for bothering, but could you add support aarch64 now since ffmpeg compilation script is now in place?
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.