Bug 282792

Summary: emulators/ppsspp: update to 1.18.1, bundle static ffmpeg-3.0.2 for improved PSP game compatibility
Product: Ports & Packages Reporter: Kevin Reinholz <kreinholz>
Component: Individual Port(s)Assignee: Daniel Engberg <diizzy>
Status: New ---    
Severity: Affects Only Me CC: diizzy, kreinholz
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
Ports tree patch updating emulators/ppsspp to 1.18.1 with proposed multimedia/ffmpeg3 port as build dependency
none
Updated patch updating emulators/ppsspp to 1.18.1 with bundled multimedia/ffmpeg3 as static build dep none

Description Kevin Reinholz 2024-11-16 00:47:58 UTC
Created attachment 255210 [details]
Ports tree patch updating emulators/ppsspp to 1.18.1 with proposed multimedia/ffmpeg3 port as build dependency

Proposed patch updating emulators/ppsspp from 1.17.1 to latest upstream 1.18.1, and bundling proposed multimedia/ffmpeg3 port from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282188
Comment 1 Kevin Reinholz 2024-11-17 04:07:56 UTC
Created attachment 255228 [details]
Updated patch updating emulators/ppsspp to 1.18.1 with bundled multimedia/ffmpeg3 as static build dep

Updated patch to update emulators/ppsspp to version 1.18.1 and replace system ffmpeg with proposed multimedia/ffmpeg3 as static build dep.

Replaced files/patch-no-egl with files/patch-no-egl-plus-warnings-fix, which backports a fix from PPSSPP upstream Commit 55aa1ff (https://github.com/hrydgard/ppsspp/commit/55aa1ff66e80a22338bdf30f7256ff985a6e1b08) to suppress clang warnings during build due to gcc-specific flag running regardless of compiler used.

Bumped versions of bundled build deps miniupnpd, cpu_features, ppsspp-debugger, and rcheevos that I missed the first time around.
Comment 2 Kevin Reinholz 2024-11-21 14:57:34 UTC
(In reply to Kevin Reinholz from comment #1)

Caught a minor mistake in my updated patch:

google-cpu_features doesn't need to be updated. The version targeted in the current emulators/ppsspp port is:

google-cpu_features-v0.8.0-27-gfd4ffc1

And my erroneous update to:

google-cpu_features-v0.9.0-gfd4ffc1

Is the same exact git commit, albeit with the wrong release number before it.

Commit fd4ffc1 is indeed 27 commits ahead of the v0.8.0 release. The v0.9.0 release is another 8 git commits ahead of that.

My erroneous update doesn't seem to change what version of google-cpu_features is downloaded during the build process, aside from the checksum, but it is still a mistake since commit fd4ffc1 is pre-v0.9.0.