Package Details: citra 1:r10114.864414f-2

Git Clone URL: https://aur.archlinux.org/citra.git (read-only, click to copy)
Package Base: citra
Description: An experimental open-source Nintendo 3DS emulator/debugger
Upstream URL: https://github.com/PabloMK7/citra
Keywords: 3ds emulator nintendo
Licenses: GPL-2.0-or-later
Conflicts: citra-appimage
Submitter: username227
Maintainer: username227 (HurricanePootis)
Last Packager: HurricanePootis
Votes: 5
Popularity: 0.37
First Submitted: 2024-05-20 21:32 (UTC)
Last Updated: 2025-03-18 04:04 (UTC)

Latest Comments

1 2 Next › Last »

username227 commented on 2025-03-23 05:14 (UTC)

OK it looks like Pablo went to great lengths to delete the source code from his repository so it's unlikely that he will put it back up on his own repository.

I did manage to find the unified-source file needed for the build on the internet, and i know it's the right one because it passed the validity check. I have forked what I believe to be pablo's last source code from another fork of his repository, and I have uploaded the unified sources file onto my repository copy. I have updated the pkgbuild to look for the file there and it should work again.

username227 commented on 2025-03-23 02:34 (UTC)

Alternatively, if anybody has the source file in a cached build directory, please host it somewhere, i'll download it and host it on a github repo and we can use that going forward. If neither of these options work out, I will revamp the build process but trust me, that would be a longer build.

username227 commented on 2025-03-23 02:19 (UTC)

the link, which was valid just a few days ago, was a unified-source link which didn't require any of the externals. If we use the tag link, we will need to make major revisions to the pkgbuild to put back all of the externals into it. This can be done. But it's easier if we can figure out what happened to the link. I sent a message on discord to Pablo who was the developer behind citra on azahar's discord site, hopefully he'll respond at some point.

bananasgomoo commented on 2025-03-22 15:17 (UTC)

fyi getting this following 404 error when attempting to download the new update:

curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://github.com/PabloMK7/citra/releases/download/r608383e/citra-unified-source-20240927-608383e.tar.xz

I think the link should probably be https://github.com/PabloMK7/citra/archive/refs/tags/r608383e.tar.gz but I'm not sure.

HurricanePootis commented on 2025-03-18 03:33 (UTC)

@allenhs Report bugs to comment sections, not flag-out-dates. This is more helpful and keeps a track of what happens. Try again.

username227 commented on 2024-12-02 19:37 (UTC)

@claymorwan, I think it just needs to be rebuilt against the updated dependency. I updated the pkgver to force a rebuild. Let me know if this helps.

claymorwan commented on 2024-12-02 18:04 (UTC)

Y'all know if this is aur related or not ?

$ citra
citra: error while loading shared libraries: libSPIRV.so.14: cannot open shared object file: No such file or directory

HurricanePootis commented on 2024-08-13 01:39 (UTC)

Hello, as the past maintainer for citra related projects on AUR, I have some suggestions for this package that you may have already ready at lime3ds, citra-git, and lime3ds-git.

  1. Change license from GPL-2.0 to GPL-2.0-only to be SPDX compliant
  2. Remove the DCMAKE_C_FLAGS and DCMAKE_CXX_FLAGS. Citra cannot build due to the Warrning Protection from Foritfy Source. However, that does not mean the rest of the Arch build flags should be disregarded. Instead, in the patch, I have removed -Wp,-D_FORTIFY_SOURCE=3 using sed, and the project builds fine with the default Arch flags defined in /etc/makepkg.conf. Therefore, there is no longer any reason to disable buildflags in options().
  3. Don't use the Release cmake build type, as explained here. Instead, use the None build type; this goes hand in hand with point 2.
  4. Remove libc++. Citra has no specific need for libc++, nor does it call upon it during a clean chroot build.
  5. Use system libraries. This cuts the amount of files needed to compile in almost half.
  6. Use ThinLTO instead of normal LTO with clang to speed up build times.
  7. Add conflicts and provides as this is a git package.
  8. Missing dependencies.

Here is the link to the patch file.

username227 commented on 2024-07-11 11:02 (UTC)

good idea. thanks!

1 2 Next › Last »