Package Details: torzu-git r27206.eaa9c9e3a-1

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: 2.51
First Submitted: 2024-06-02 14:39 (UTC)
Last Updated: 2025-03-17 00:33 (UTC)

Required by (0)

Sources (27)

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.

Latest Comments

1 2 3 Next › Last »

sukanka commented on 2025-03-21 00:39 (UTC)

Well, some of them just copied from yuzu-ea, focus on fixes for the latest boost and fmt (regarding on cpp and header files). As torzu and citron are under development (unlike yuzu), they may be outdated or unnecessary, I will try to remove them.

Others are added by me to make it utilize system libraries, or to fix some building errors.

username227 commented on 2025-03-20 21:02 (UTC)

@sukanka, at risk of sounding ignorant, can you explain to me what the sed command does in the prepare function? Tried to research but came up more confused. thanks!

sukanka commented on 2025-03-19 14:10 (UTC) (edited on 2025-03-21 00:40 (UTC) by sukanka)

I made a working PKGBUILD by adapting changes from the previous yuzu-early-access. HERE is my PKGBUILD. Note: it needs to be built in chroot.

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.

username227 commented on 2025-03-14 20:16 (UTC)

@00x

Interesting. Thanks for the info. Lately, though, I've been getting a different error, again, only when I build outside of a chroot:

CMake Error at externals/glad/CMakeLists.txt:10 (create_target_directory_groups):
  Unknown CMake command "create_target_directory_groups".

Happens both in this package and with citron, only when building outside of a chroot.I remember this happening with suyu also last year, but those packages are gone now. Not sure how to fix except to continue to build in a chroot, because I'm not sure which package is causing the problem.

00x commented on 2025-03-13 22:48 (UTC)

@username227

If anybody knows what is causing this and can assist with a fix, please reach out to me. Thanks.

The problem appears to be that cmake tries to use the system SPIRV-Headers if they're installed, even when -DYUZU_USE_EXTERNAL_VULKAN_SPIRV_TOOLS=ON is set. I got around that by removing the find_package(SPIRV-Headers) line from externals/CMakeLists.txt

awh commented on 2025-01-29 17:02 (UTC) (edited on 2025-01-29 17:06 (UTC) by awh)

@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.

username227 commented on 2025-01-29 15:31 (UTC)

@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.

hypnagogic commented on 2025-01-29 15:06 (UTC)

This package seems to rebuild every time I update with paru. Is this expected behavior?