Package Details: yuzu-mainline-git r15515.8642321-1

Git Clone URL: https://aur.archlinux.org/yuzu-mainline-git.git (read-only, click to copy)
Package Base: yuzu-mainline-git
Description: An experimental open-source Nintendo Switch emulator/debugger
Upstream URL: https://github.com/yuzu-emu/yuzu-mainline
Keywords: emulator game qt switch
Licenses: GPL2
Conflicts: yuzu-canary-git, yuzu-git
Provides: yuzu, yuzu-cmd
Submitter: bscubed
Maintainer: bscubed
Last Packager: bscubed
Votes: 12
Popularity: 2.26
First Submitted: 2019-11-24 04:03
Last Updated: 2020-07-24 14:50

Pinned Comments

bscubed commented on 2019-11-24 17:42

If you're wondering what happened to yuzu-canary-git, read more here https://yuzu-emu.org/entry/yuzu-migration/ TL;DR: yuzu canary and yuzu nightly are being replaced by a single package, yuzu-mainline. This is the mainline build and contains untested, bleeding-edge features over yuzu stable.

bscubed commented on 2018-11-12 01:49

Some things to note: This is an unofficial package, thus is not officially supported by the Yuzu team. Please don't ask for help on their forums or discord if you run into issues with this build, as it might devote import development resources to a bug that might have to do with running Yuzu on an unofficial platform. If you encounter an issue, feel free to comment on this package and I'll try to point you in the right direction.

Also, this build is in active development. Builds might break every once in a while.

If you're looking for the QT version of this package, it has now been merged in this package. No need for two packages anymore, and no need to compile everything twice.

Thanks for using my package and have a nice day! :)

Latest Comments

1 2 3 4 Next › Last »

maxweiss commented on 2020-09-12 18:40

@aaulia I also experienced the exact same thing. Built fine, but failed first test with exactly same output you had.

aaulia commented on 2020-07-28 04:34

I got it to build, but failed on the unit-test. :-?

[100%] Built target yuzu
==> Starting check()...
Running tests...
Test project /home/aaulia/.cache/yay/yuzu-mainline-git/src/yuzu/build
    Start 1: tests
1/1 Test #1: tests ............................Child aborted***Exception:   3.43 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   3.44 sec

The following tests FAILED:
     1 - tests (Child aborted)
Errors while running CTest
make: *** [Makefile:137: test] Error 8
==> ERROR: A failure occurred in check().
    Aborting...
error making: %!s(func() string=0x5576be556bb0)

XRaTiX commented on 2020-07-21 23:51

@nissen22 I was able to install yuzu with the outdated fmt in the repos and installed conan,thanks for the tip!

nissen22 commented on 2020-07-21 06:48

I think this package needs conan as a makedep. The error mentioned by ibrokemypie is fixed by installing conan. https://aur.archlinux.org/packages/conan/

It seems as though conan is only needed because of the outdated fmt in the Arch repos though, will try building without it when fmt is updated.

ibrokemypie commented on 2020-07-17 12:18

Currently does not build, requires fmt >= 7.9 (arch repos only have 6.2.1), and after installing fmt-git it still fails to build after configuring

-- Configuring done
CMake Error in externals/dynarmic/src/CMakeLists.txt:
  Imported target "Boost::boost" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in externals/dynarmic/src/CMakeLists.txt:
  Imported target "Boost::boost" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in src/common/CMakeLists.txt:
  Imported target "Boost::context" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in src/common/CMakeLists.txt:
  Imported target "Boost::context" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in src/core/CMakeLists.txt:
  Imported target "nlohmann_json::nlohmann_json" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in src/core/CMakeLists.txt:
  Imported target "nlohmann_json::nlohmann_json" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in src/web_service/CMakeLists.txt:
  Imported target "nlohmann_json::nlohmann_json" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in src/web_service/CMakeLists.txt:
  Imported target "nlohmann_json::nlohmann_json" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



-- Generating done

bscubed commented on 2020-06-04 00:22

yuzu has been updated to include the necessary dependencies. One of the dependencies needed to run yuzu after it's built is qt5-base 5.15 which was very recently pushed to the arch repositories. If yuzu fails to open after installation with an error saying qt-base 5.15 not found, you need to update your system first. The reason I say this is because qt-base was at version 5.14 when the 5.15 requirement was merged upstream.

maxi_jac commented on 2020-05-19 14:14

Hello, missing dependencies I had to add to build: 'catch2' 'fmt' 'nlohmann-json'

Terence commented on 2020-02-28 15:30

@bscubed I see, thanks for explaining, as long as you are aware it's usually the user responsibility to do that. Talking about improving user experience, can you give my draft PKGBUILD a try? This will prevent having to reclone each submodule when doing a clean build.

bscubed commented on 2020-02-08 02:15

@Terence Thank you for your suggestion, however, since I am the one who wrote the pkgver() function for my package, I know how it works and there are several key reasons I choose to bump the version anyways. The first is because many users install packages through AUR helpers and rely on these managers to notify them of updates. Bumping the version allows it to show up in the manager they use along with other updates keeping yuzu up to date with minimal user interaction. The second reason is because after I test my packages for errors (which I do at least weekly) the pkgver is updated, so why not update the package anyways? Updates are a sign a maintainer is active, and still cares about the project they committed to. And if I can make updates easier for the users of my package, I will.

Terence commented on 2020-01-30 22:29

@bscubed This is a VCS package which has a pkgver() function so you shouldn't update the PKGBUILD just to bump the version because it's the responsibility of the users to track updates.