Also, when you put in a pkgver() function, be sure to put epoch=1 in the PKGBUILD since Pacman will compare the git revision number to 20130726 and likely believe it to be an older version.
Search Criteria
Package Details: ppsspp-assets-git 1.17.1.r785.cbdb2a37eb-1
Package Actions
| 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-assets |
| Provides: | ppsspp-assets |
| Submitter: | libcg |
| Maintainer: | loathingkernel |
| Last Packager: | loathingkernel |
| Votes: | 43 |
| Popularity: | 0.23 |
| First Submitted: | 2012-11-05 20:36 (UTC) |
| Last Updated: | 2024-06-21 11:26 (UTC) |
Dependencies (14)
- clang (llvm-rocm-gitAUR, llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- cmake (cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- glew (glew-libepoxyAUR, glew-waylandAUR, glew-osmesa-gitAUR, glew-wayland-gitAUR, glew-gitAUR) (make)
- glu (glu-gitAUR) (make)
- libglvnd (libglvnd-gitAUR) (make)
- libpng (libpng-gitAUR, libpng-apngAUR) (make)
- libzip (libzip-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- sdl2 (sdl2-gitAUR, sdl2-compat-gitAUR) (make)
- sdl2_ttf (make)
- snappy (snappy-gitAUR) (make)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat) (make)
Required by (2)
- libretro-ppsspp-git (requires ppsspp-assets) (optional)
- ppsspp-git
Sources (2)
Schala commented on 2013-07-31 09:29 (UTC)
Schala commented on 2013-07-28 23:48 (UTC)
You need to put in a pkgver() function that will auto-set the pkgver. Here's one of mine for an example
pkgver() {
cd "$srcdir/${pkgname%-*}"
echo $(git rev-list --count master)
}
This will set the pkgver to the revision number for the repo.
libcg commented on 2013-07-28 11:08 (UTC)
Schala, I don't understand what you want.
Schala commented on 2013-07-28 01:52 (UTC)
Can you update this for Pacman 4.1? Thanks
libcg commented on 2013-07-26 20:47 (UTC)
Fixed LDFLAGS, fixed dependancies, removed PPSSPPHeadless.
kokoko3k commented on 2013-07-23 15:35 (UTC)
it fails for me on i686:
"Linking CXX executable PPSSPPSDL
/var/abs/local/yaourtbuild/ppsspp-git/src/ppsspp/ffmpeg/linux/x86_64/lib/libavformat.a: impossibile leggere i simboli: File format not recognized"
mvdan commented on 2013-07-12 13:25 (UTC)
I don't know how can some people compile from master without the extra LDFLAGS - perhaps there's something I'm missing? Flagging as out of date.
libcg commented on 2013-07-09 14:51 (UTC)
Well, you are using the trunk version so you should expect bugs.
Use this instead: https://aur.archlinux.org/packages/ppsspp/
Or wait until it's fixed.
<deleted-account> commented on 2013-07-09 11:20 (UTC)
i have been compile successfully,but i can't run this program. it show me
/usr/bin/PPSSPPSDL: line 3: 14340 Segmentation fault (core dumped) ./PPSSPPSDL i don't know how to do
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.