Package Details: gzdoom 4.1.3-1

Git Clone URL: https://aur.archlinux.org/gzdoom.git (read-only)
Package Base: gzdoom
Description: Advanced Doom source port with OpenGL support
Upstream URL: http://www.zdoom.org/
Licenses: GPL3, BSD, LGPL3, custom:dumb
Replaces: gzdoom1
Submitter: None
Maintainer: grubber
Last Packager: grubber
Votes: 111
Popularity: 1.962887
First Submitted: 2009-02-22 22:28
Last Updated: 2019-06-10 10:15

Dependencies (33)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

MadTux commented on 2016-02-08 08:44

Do you think you could update to 2.1.0?

http://forum.drdteam.org/viewtopic.php?f=23&t=6791

ozky commented on 2015-12-04 15:30

Yes it needed i got my own way to do it.......Builded it in seperate system and extracted it to local folder and added it to enyo doom as it can use manually added doom engine,no gtk but brutal doom and lot others get working. :)

grubber commented on 2015-11-30 19:02

gtk2 is required for the IWAD selection dialog and gxmessage is needed for the crash log window. Both are features I want in the build to be on par with the official Windows build, so they won't be removed, sorry.

ozky commented on 2015-11-30 18:44

You may grubber add gtk2 require as optional it's only needed to gui as without it you can use it with enyo-doom.

http://zdoom.org/wiki/Compile_GZDoom_on_Linux
GTK2 (optional)

pacman -S --needed gcc make zlib sdl sdl2 libjpeg-turbo nasm tar bzip2 gtk2 cmake git \
fluidsynth libgme openal timidity++ mesa glu glew

I compiled it with removing gtk2 and gxmessage from pkgbuild and it compiles with no error.

jclaudio commented on 2015-10-09 06:07

I cannot use this because of fmodex4.26.36

Anyone else having this problem?

claymore commented on 2015-03-10 16:43

wrong SDL lib dependency. It should be SDL2. Because of that, it does not compile out of the box.

Fincer commented on 2015-02-06 02:30

Thank you for informing me about the GIT version you already have available here.

Well, let me clarify: The current PKGBUILD script grabs correct gzdoom version from Github. However, the problem is that if pure tar.gz archive is used, gzdoom doesn't recognize version number correctly, leading to <unknown version> issue.

[fincer@fincer-laptop fincer]$ gzdoom
GZDoom <unknown version> - - SDL version
Compiled on Feb 6 2015
Using video driver x11

And this is what I refer to when talking about "messes with version numbering".

I asked GZDoom developer Graf Zahl about this issue and he stated:

"Do you have the git command line utilities installed? The broken version number suggests you have not. With this you can also retrieve the source for any branch or tag, including the release versions."

Doing the installation by suggested git way gets the version number shown correctly in the program, too. Regardless of available tar.gz archives in Github. That's why I think git way is the only correct way to install this package - unless you want <unknown version> to be visible while running the program.

Otherwise, the current compilation script works very fluently and builds gzdoom version 2.0.04 as suggested in the AUR package title. As you already said.

Fincer commented on 2015-02-06 02:12

Yes, and that that "release tarball" doesn't contain version numbering for the program itself. The current compilation method leads to <unknown version> which is not desirable functionality:

[fincer@fincer-laptop fincer]$ gzdoom
GZDoom <unknown version> - - SDL version
Compiled on Feb 6 2015
Using video driver x11

GZDoom developer Graf Zahl stated when asked about <unknown version> (got by compiling with the current tar.gz method):

"Do you have the git command line utilities installed? The broken version number suggests you have not. With this you can also retrieve the source for any branch or tag, including the release versions."

And doing the installation by suggested git way gets the version number shown correctly. Regardless of available tar.gz archives in Github.

[fincer@fincer-laptop gzdoom]$ gzdoom
GZDoom g2.0.04 - 2014-12-21 14:58:11 +0100 - SDL version
Compiled on Feb 4 2015
Using video driver x11

Fincer commented on 2015-02-06 02:06

Yes, and that that "release tarball" doesn't contain version numbering for the program itself. Your current method leads to <unknown version> which is not desirable functionality:

[fincer@fincer-laptop fincer]$ gzdoom
GZDoom <unknown version> - - SDL version
Compiled on Feb 6 2015
Using video driver x11

GZDoom developer stated when asked about <unknown version> (got by compiling with your tar.gz method):

"Do you have the git command line utilities installed? The broken version number suggests you have not. With this you can also retrieve the source for any branch or tag, including the release versions."

And doing the installation by suggested git way gets the version number shown correctly. Regardless of available tar.gz archives in Github.

[fincer@fincer-laptop gzdoom]$ gzdoom
GZDoom g2.0.04 - 2014-12-21 14:58:11 +0100 - SDL version
Compiled on Feb 4 2015
Using video driver x11

grubber commented on 2015-02-04 21:36

The PKGBUILD doesn't mess with anything, it uses only what is provided in the release tarball. If you want to build from git, you should use <https://aur.archlinux.org/packages/gzdoom-git/>.