Search Criteria
Package Details: crispy-doom 7.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/crispy-doom.git (read-only, click to copy) |
|---|---|
| Package Base: | crispy-doom |
| Description: | Vanilla-compatible enhanced Doom engine |
| Upstream URL: | http://fabiangreffrath.github.io/crispy-doom |
| Licenses: | GPL2 |
| Submitter: | chungy |
| Maintainer: | chungy |
| Last Packager: | chungy |
| Votes: | 15 |
| Popularity: | 0.000546 |
| First Submitted: | 2014-06-01 00:10 (UTC) |
| Last Updated: | 2024-08-15 07:53 (UTC) |
Dependencies (10)
- fluidsynth (fluidsynth-gitAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libpng (libpng-gitAUR, libpng-apngAUR)
- libsamplerate (libsamplerate-gitAUR)
- sdl2_mixer
- sdl2_net
- python (python37AUR, python311AUR, python310AUR) (make)
- freedmAUR (freedm-gitAUR) (optional) – Free deathmatch game
- freedoom1 (freedoomAUR, freedoom-gitAUR) (optional) – Free Ultimate Doom-compatible game
- freedoom2 (freedoomAUR, freedoom-gitAUR) (optional) – Free Doom II-compatible game
Required by (1)
- qzdl-git (optional)
Latest Comments
1 2 Next › Last »
chungy commented on 2024-05-11 21:11 (UTC)
@Beethoven-n the file names are already in the standard format demanded by the desktop entry specification and appstream specifications. You could try to take it up with the upstream project, but it's unlikely to change (especially not to a file name with a space in it :P)
Beethoven-n commented on 2024-05-10 18:59 (UTC)
the Crispy Setup .desktop launcher is not named after the
Name=field, instead installing to/usr/share/applications/io.github.fabiangreffrath.Setup.desktop. it should install to/usr/share/applications/Crispy\ Setup.desktop, to be consistent with other non-Flatpak applications.<deleted-account> commented on 2023-05-08 12:28 (UTC)
The Crispy Setup .desktop launcher doesn't work. The crispy-setup binary isn't shipped with the package
Edit: Fixed on the same day
sramey40 commented on 2021-08-25 01:04 (UTC)
The cripsy doom setup .desktop launcher is created incorrectly, and it tries to run "crispy-setup", but it should run "crispy-doom-setup" instead.
SpacingBat3 commented on 2020-09-30 20:27 (UTC)
Could you update PKGBUILD to include
aarch64in PKGBUILD? I ran this on my RPi4B with aarch64 (arm64) OS and this works as great as onchocolate-doom(those engines are pretty similar when compared).dleslie commented on 2020-09-10 15:29 (UTC)
Likewise, this builds and runs fine on
aarch64SpacingBat3 commented on 2020-06-16 11:26 (UTC) (edited on 2020-06-18 22:09 (UTC) by SpacingBat3)
I successfully built crispy-doom via "yay" using architecture "aarch64" – this arch with exactly this name should be added now to PKGBUILD, so other package managers will be able to build it from AUR (like pamac, for example).
EDIT: So my request is to change line:
arch=('i686' 'x86_64')toarch=('i686' 'x86_64' 'aarch64')in PKGBUILD.MindfulProtons commented on 2020-05-16 17:05 (UTC) (edited on 2020-05-16 17:06 (UTC) by MindfulProtons)
It seems that this package is broken with GCC 10, according to this Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957110
Trying to build it results in this error:
/usr/bin/ld: doom/libdoom.a(g_game.o):/home/proton/.cache/yay/crispy-doom/src/crispy-doom-crispy-doom-5.8.0/src/doom/../../src/v_trans.h:50: multiple definition of 'cr_t'; v_trans.o:/home/proton/.cache/yay/crispy-doom/src/crispy-doom-crispy-doom-5.8.0/src/v_trans.h:50: first defined here, with a few more that are quite similar.przemko27 commented on 2017-01-26 16:04 (UTC)
chungy commented on 2017-01-19 20:55 (UTC)
1 2 Next › Last »