Package Details: duckstation-git 0.1.r9727.g66bef3e3e-1

Git Clone URL: https://aur.archlinux.org/duckstation-git.git (read-only, click to copy)
Package Base: duckstation-git
Description: A Sony PlayStation (PSX) emulator, focusing on playability, speed, and long-term maintainability (git version)
Upstream URL: https://github.com/stenzek/duckstation
Keywords: emulator game gaming psone psx
Licenses: cc-by-nc-nd-4.0
Conflicts: duckstation
Provides: duckstation
Submitter: jackdroido
Maintainer: eugene
Last Packager: eugene
Votes: 31
Popularity: 0.92
First Submitted: 2020-04-25 18:24 (UTC)
Last Updated: 2025-09-21 13:52 (UTC)

Required by (0)

Sources (11)

Pinned Comments

eugene commented on 2025-09-03 18:12 (UTC)

The 'versions' file now includes a curious disclaimer that specifically forbids any packaging scripts from using it.

PN123 commented on 2025-09-03 17:44 (UTC)

Stumbled upon a problem in prepare() while trying to update:

The build fails at this grep. It doesn't find anything because the version strings have been moved to a different file.

dep_ver=$(grep -Po "(?<=^$dep_var=).+" "$deps_script" )

They are now listed here: $srcdir/duckstation/scripts/deps/versions

Latest Comments

1 2 3 4 5 6 .. 17 Next › Last »

SimplyCEO commented on 2025-10-02 14:55 (UTC)

Can we use something like Gentoo build?

It looks easier to read and appears to use system libraries instead of the provided ones from repository.

Just run CMake and look for the system libraries. No need to run his script. makepkg can run in a chroot to avoid overwritting system libraries and breaking other software. It is not much of a problem.

Neros commented on 2025-09-27 12:44 (UTC)

Broken again:

==> Starting prepare()...
==> ERROR: A failure occurred in prepare().
    Aborting...

eugene commented on 2025-09-20 16:39 (UTC)

It seems build is broken not only for us. The only thing that helps official build is hot dependencies cache. There is not such commit (3ebbfd45645650c4940bf0f3b4d25ab913466bb0) in stenzek.cpuinfo repo

Neros commented on 2025-09-20 10:24 (UTC)

Broken again:

==> Starting prepare()...
Checking out 4daf9d466ad00897f755163dd26f528d14e1db44 for stenzek.shaderc...
Checking out vulkan-sdk-1.4.321.0 for spirv-cross...
Checking out 3ebbfd45645650c4940bf0f3b4d25ab913466bb0 for stenzek.cpuinfo...
fatal: unable to read tree (3ebbfd45645650c4940bf0f3b4d25ab913466bb0)
==> ERROR: A failure occurred in prepare().
    Aborting...

Neros commented on 2025-09-14 10:25 (UTC) (edited on 2025-09-14 14:27 (UTC) by Neros)

@eugene: I can build it with the new PKGBUILD but when launching duckstation-qt I have an error window with Process... Failed in the title and an OK button and it exits by pressing it (no error in the log).

EDIT: fixed, thanks

raziel100 commented on 2025-09-14 01:30 (UTC)

if anyone is having the problem that @Neros said, just do a

git revert --no-edit 6126209a25c279c6b3cffab012e9a52c84113d92

in # unbreak the build, after cd "$srcdir/duckstation", and it will build normaly again!

Neros commented on 2025-09-13 13:18 (UTC)

Broken again:

==> Entering fakeroot environment...
==> Starting package()...
ninja: Entering directory `build'
ninja: error: unknown target 'install'
==> ERROR: A failure occurred in package().
    Aborting...

Probably because of this commit:
https://github.com/stenzek/duckstation/commit/84c6be74d3f1e2a7e75c037dbb4a4cca79e23e4a

raziel100 commented on 2025-09-04 18:47 (UTC)

So, the way to help fix the issue between us and him, is to break this pkgbuild, making more difficult for someone to use it? because even the dep_ver issue that had already been apointed by hadn't been adressed at all, the build is still failing because of the changes in upstream, nothing was adressed, is still broken, just that now is even more broken than before

HurricanePootis commented on 2025-09-04 16:03 (UTC)

@loathingkernel

In my CMake arguments, I'm doing stuff like -DSDL3_DIR="$srcdir/build-deps/lib/blah/blah/blah, in the end, that ends up linking my duckstation-qt to the specific location of the binary. However, since you did -DCMAKE_PREFIX_PATH="$PWD"/build-deps \ it somehow changes the behavior. I don't know which method of doing is "more correct". But, I will look into it cause it seems a lot simpler.