| Git Clone URL: | https://aur.archlinux.org/torzu-git.git (read-only, click to copy) |
|---|---|
| Package Base: | torzu-git |
| Description: | Torzu is a fork of yuzu, the world's most popular, open-source, Nintendo Switch emulator. It is written in C++ with portability in mind. |
| Upstream URL: | https://notabug.org/litucks/torzu |
| Keywords: | emulator nintendo switch |
| Licenses: | GPL-3.0-or-later |
| Conflicts: | torzu |
| Provides: | torzu |
| Submitter: | username227 |
| Maintainer: | username227 |
| Last Packager: | username227 |
| Votes: | 11 |
| Popularity: | 0.72 |
| First Submitted: | 2024-06-02 14:39 (UTC) |
| Last Updated: | 2025-05-25 05:31 (UTC) |
@username227 I tried to add IgnoreDevelSource = torzu-git to paru.conf, but it doesn't seem to fix this despite what the manpage describes ("Like IgnoreDevel but targets urls in the source=() array").
Perhaps it's a bug with paru.
edit: after doing this and then also removing any of the non "notabug.org" urls related to torzu-git from ~/.local/state/paru/devel.toml it appears to function as intended.
@hypnagogic, I actually stopped using paru for this reason.
As far as I can tell, the method that paru uses to determine when development packages need to be rebuilt has to do with a streamlined method that does not require actual downloads of the sources, and thus is much quicker. However, as a side-effect of the process, it seems to trigger a rebuild of the package every single time that any one of the submodules gets a new commit, not just the key torzu source.
I'm not 100% sure that this is the reason, but i'm fairly certain. There is a way to make paru use the other, longer method of determining when a dev package needs to rebuilt, but it's complicated, and I don't know if it can be made persistent.
This package seems to rebuild every time I update with paru. Is this expected behavior?
The crash gets fixed by building with -DYUZU_USE_EXTERNAL_VULKAN_SPIRV_TOOLS=ON
I get a crash when trying out anything with vulkan:
yuzu: /build/spirv-tools/src/SPIRV-Tools-2024.4.rc2/source/opt/propagator.cpp:265: spvtools::opt::SSAPropagator::Run(spvtools::opt::Function*)::<lambda(spvtools::opt::Instruction*)>: Assertion (!HasStatus(inst) || Status(inst) != SSAPropagator::kNotInteresting) && "Unsettled value"
@username227 if it's a problem with tests, you can disable the check stage with --nocheck to makepkg or !check in BUILDENV of /etc/makepkg.conf
hmmm...I can't get it to build now at all. it gets almost all the way to the end and fails on soemthing related to tests. I'll have to work on this more.
For whatever reason, I couldn't build unless in a chroot also, but after following @agapito's suggestion it wasn't buildable in a chroot but was buildable outside. Perhaps some builddeps were installed on my system that weren't copied into the chroot.
I suggest -DENABLE_QT6=ON \ and remove all Qt 5 packages from dependencies.
Also, remove -DCMAKE_CXX_COMPILER=/usr/bin/g++-13 \ and -DCMAKE_C_COMPILER=/usr/bin/gcc-13 \ as Gcc 13 is not needed to build this package.
Pinned Comments
username227 commented on 2025-03-17 00:35 (UTC) (edited on 2025-03-17 00:37 (UTC) by username227)
OK I got it! The solution suggested by @00x solved the spirv problem. I figured out my problem with glad by forcing the build to use dynarmic from externals. I also changed to use the system sdl2 instead of the one from externals to solve a third error related to sdl2/pipewire that I received later in the build.
Everything, in theory, should work now. Let me know if you have any issues. thanks.