Package Details: rpcs3-git 0.0.36.r17723.2f8ed1a6bd-2

Git Clone URL: https://aur.archlinux.org/rpcs3-git.git (read-only, click to copy)
Package Base: rpcs3-git
Description: A Sony PlayStation 3 emulator
Upstream URL: https://github.com/RPCS3/rpcs3
Licenses: GPL-2.0-only
Conflicts: rpcs3
Provides: rpcs3
Submitter: alucryd
Maintainer: hcorion
Last Packager: hcorion
Votes: 79
Popularity: 0.58
First Submitted: 2014-08-14 11:04 (UTC)
Last Updated: 2025-03-31 01:11 (UTC)

Latest Comments

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

Score_Under commented on 2022-11-23 18:29 (UTC) (edited on 2022-11-23 18:31 (UTC) by Score_Under)

@Smokus this is a VCS package, meaning it automatically reaches for the latest git commit and the version number provided for reference in the AUR web interface may not be accurate to what actually gets installed. Put another way, there is something of an expectation that these packages may break from time to time.

If that behaviour is undesirable, you can instead grab a different package like rpcs3-bin which seems to be manually updated to point to binaries hosted on the official github releases page.

<deleted-account> commented on 2022-11-23 16:11 (UTC)

Mind sharing under what criteria do you decide to update the version of the package?

According to RPCS3'S GH release page, they say the following:

These are NOT stable builds. RPCS3 is a rolling release software without stable builds. These are random tags we do from time to time. Do NOT use the branch from these tags to package RPCS3.

Neko-san commented on 2022-11-07 23:34 (UTC)

Yeah, git -c protocol.file.allow=always submodule update is the correct way

Score_Under commented on 2022-11-04 12:37 (UTC)

The topic there suggested a less hacky workaround: git -c protocol.file.allow=always submodule update -- would that be suitable for this package?

kode54 commented on 2022-10-20 01:43 (UTC)

Oh, crud. I forgot, I was only maintainer of the "stable" package that stuck to the useless tags on the repo, when this project doesn't do tagged releases at all.

kode54 commented on 2022-10-20 01:42 (UTC)

As the topic suggests, this is using an internal script to avoid a security requirement. I await further discussion in the topic you linked.

italoghost commented on 2022-10-20 01:13 (UTC)

There was an update on git. It is necessary to change the PKGBUILD, replacing

 git submodule update

with

git submodule--helper update

There were some discussions about this subject on this post.

atticf commented on 2022-06-11 16:00 (UTC)

I needed to explicitly add -DUSE_SYSTEM_WOLFSSL=OFF in the cmake arguments to allow cmake to find the package:

-- Checking for module 'wolfssl>=4.7.0'
--   Package 'wolfssl', required by 'virtual:world', not found
CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:605 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPkgConfig.cmake:827 (_pkg_check_modules_internal)
  3rdparty/wolfssl/CMakeLists.txt:3 (pkg_check_modules)

Please consider adding it

Neko-san commented on 2022-05-23 17:36 (UTC)

@patlefort RPCS3 hasn't had building issues for LTO in a while, I'm actually somewhat the cause of this new cmake error

I had reported some bugs that involved LTO but ultimately were "solved" by just enforcing the lack of LTO in the build system. The original issue I had reported was a floating point error but I don't think it was actually fixed because the initial response was a commit PR to prevent LTO instead. This was partially due to the fact that Qt doesn't always like LTO (can cause launch crashes), but now you at least have the full picture as to why no time was really spent on it instead.

patlefort commented on 2022-05-23 06:47 (UTC)

Rpcs3 now error out when LTO is enabled:

CMake Error at CMakeLists.txt:137 (message):
  Rpcs3 doesn't support building with LTO, use -DDISABLE_LTO=TRUE to
  force-disable it

I think options=(!lto) should be used.

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