Package Details: pcsx2-git 2.3.10.r0.g5441c7ed59-1

Git Clone URL: https://aur.archlinux.org/pcsx2-git.git (read-only, click to copy)
Package Base: pcsx2-git
Description: A Sony PlayStation 2 emulator
Upstream URL: https://github.com/PCSX2/pcsx2
Licenses: GPL-3.0+
Conflicts: pcsx2
Provides: pcsx2
Submitter: alucryd
Maintainer: weirdbeard (xiota)
Last Packager: weirdbeard
Votes: 130
Popularity: 0.35
First Submitted: 2014-03-26 14:17 (UTC)
Last Updated: 2024-11-08 23:36 (UTC)

Dependencies (32)

Required by (3)

Sources (8)

Pinned Comments

weirdbeard commented on 2024-08-17 03:40 (UTC)

https://github.com/PCSX2/pcsx2/pull/11632

This package now enables Cmake Package mode proper. PCSX2 will here on, be installed in the package standard folders /usr/bin, /usr/share, /usr/lib. Following the XDG standard pcsx2's config files remain in .config/PCSX2

In order to ensure a proper and clean upgrade. Uninstall this package COMPLETELY and clear cache before reinstalling.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 66 Next › Last »

rodrigo21 commented on 2024-06-06 02:18 (UTC) (edited on 2024-06-06 02:19 (UTC) by rodrigo21)

@xiota Same error.

At least OpenGL is working fine.

rodrigo21 commented on 2024-06-05 13:31 (UTC)

@xiota It's the Log Window in Tools > Enable Log Window.

@xmusjackson I already tried your package built in a clean chroot and had the same error.

weirdbeard commented on 2024-06-05 05:01 (UTC)

@xiota, oh trust me. I have a PKGBUILD that works and does that, that a buddy of mine drafted up.

As for the issues you listed

  1. I'll likely change the patched shaderc to match what's on the pcsx2 repo and yeah for them I could semi see that being an issue? But 99.9% of the time he's kept the two in sync with each other, IE. What's pushed to Duck is pushed to pcsx2 vice versa if it's applicable given one's a PS1 emu and the other's a PS2 emu

  2. Its pulling the patch from the repo directly so patch wise not likely, and I have plenty of eyes and sources to warn me when there's a patch update that might bork like a version change in shaderc or what have you.

@xmusjackson: Yes, yes I am. And Xiota's the one that helped me figure out the path move with shaderc hence him being able to answer somewhat. That said as for it working for you and not me, I've had countless times when maintaining these packages where things worked for person A, not person B, like with rodrigo's issue. I have another guy on Discord (Assuming rodrigo isn't the same guy) that has that same issue and it still doesn't work for him either way

Discord guy is able to run it with the flatpak since its basically a glorified VM with ubuntu dependencies but not with the package no matter what way it is or isn't built.

I feel having the package separated like this prevents a good amount of those kinds of issues from occurring with a direct patch.

Also, if we want to keep having back-and-forths like this is fine here since I get the emails, but I'm also available on Discord (weirdbeardgame)

xmusjackson commented on 2024-06-05 04:35 (UTC) (edited on 2024-06-05 05:01 (UTC) by xmusjackson)

@weirdbeard Are you building in a clean chroot? I've had no such linker issues when building altogether and I'm just following the process used when building the appimage. You can build from my repo to see for yourself. However, having a separate package for this library could be okay even, especially if you think there could be other packages that want to use this specific patchset, but you probably shouldn't copy the library from one package to another, you should rather build pcsx2 and link it with the library in place (/usr/lib/shaderc-non-semantic-debug). You could replace -DCMAKE_SKIP_RPATH with -DCMAKE_INSTALL_RPATH="/usr/lib/shaderc-non-semantic-debug" -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON unless there's something further I'm missing.

@rodrigo21 I ran into the same issue a few days ago when I first forked this package. PCSX2 is looking for a function added and exported by the patchset within what's likely the upstream shaderc (it's probably using the one present in /usr/lib. It's also possible you have an outdated version of shaderc-non-semantic-debug installed, which would require rebuilding and installing that package and then rebuilding pcsx2, or you could try building from my repo after the latest commit which reverts to using an explicit rpath.

@xiota Why did you respond to my comment as though you were the maintainer? I was replying to them when you posted your reply; I thought you were a comaintainer or something.

weirdbeard commented on 2024-06-05 04:03 (UTC)

To further clarify, one of the major issues I had, had was linking to glslang and spriv when building locally. Something the package version has no issue with and ended up in the ppa having to be manually patched

weirdbeard commented on 2024-06-05 03:58 (UTC)

Because when you try to in a friendly manner apply the patched shaderc directly to pcsx2 things get sideways in a lot of ways very quickly. You'll end up eventually modifying patches. It's something about manually building it together with PCSX2 in the AUR environment that caused a bunch of linker and other issues.

My earlier comment was meant to display the maintainer for the ubuntu PPA had similar issues and it went ... Interesting.

The other issue is, if there's anymore patched updates that cause similar issues. I feel it could be better mitigated by keeping it separate from the pcsx2 package. And, having a separate AUR package better serves, the main pcsx2 package and potentially any DuckStation packages should they end up having issues.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 66 Next › Last »