The official "ZDoom on Linux" thread.

[Gez]

If you could update the wiki article with a small explanation of the issue and how you solved it, it would be appreciated.

[Edward-san]

This is what I'm getting when I try to compile zdoom or ubuntu 11.10:

make[2]: *** [src/CMakeFiles/zdoom.dir/sound/fmodsound.o] Error 1
make[1]: *** [src/CMakeFiles/zdoom.dir/all] Error 2

I've followed the ZDoom installation guide to the letter as well. Any ideas?

There should be other messages before make errors which show the real problem, but probably the FMOD include dir or the library path aren't set correctly. Can you show here those other messages?

[Virii]

Hello. I'd like to compile ZDoom with Fluidsynth support, or at least I'm assuming it needs to be compiled in to it.

I'm currently running Debian x86_64, and I have the fluidsynth packages installed. When I went to run ZDoom, I noticed there wasn't any fluidsynth option available.

When preparing my release with debug info, I noticed that fluidsynth was not found.

Code: Select all • Expand view

~/ZDoom/relwithdebinfo # cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
-- The C compiler identification is GNU 4.6.3
-- The CXX compiler identification is GNU 4.6.3
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found BZip2: /usr/lib/x86_64-linux-gnu/libbz2.so (found version "1.0.6")
-- Looking for BZ2_bzCompressInit in /usr/lib/x86_64-linux-gnu/libbz2.so
-- Looking for BZ2_bzCompressInit in /usr/lib/x86_64-linux-gnu/libbz2.so - found
-- Found JPEG: /usr/lib/libjpeg.so 
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.6")
-- Using system zlib
-- Using system jpeg library
-- Using system bzip2 library
-- Looking for strdup
-- Looking for strdup - found
-- Looking for strndup
-- Looking for strndup - found
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of char
-- Check size of char - done
-- Check size of short
-- Check size of short - done
-- Check size of int
-- Check size of int - done
-- Check size of long
-- Check size of long - done
-- /usr/include
-- /usr/include
-- ~/ZDoom/lzma/C
-- Performing Test HAVE_NO_ARRAY_BOUNDS
-- Performing Test HAVE_NO_ARRAY_BOUNDS - Success
-- Looking for itoa
-- Looking for itoa - not found
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.26")
-- checking for module 'gtk+-2.0'
--   found gtk+-2.0, version 2.24.10
-- Found Xcursor at /usr/lib/x86_64-linux-gnu/libXcursor.so
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found.
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE 
-- Found SDL: /usr/lib/x86_64-linux-gnu/libSDLmain.a;/usr/lib/x86_64-linux-gnu/libSDL.so;-lpthread 
-- FMOD include files found at ~/ZDoom/fmod/api/inc
-- FMOD library found at ~/ZDoom/fmod/api/lib/libfmodex64-4.26.36.so
-- Could NOT find FluidSynth (missing:  FLUIDSYNTH_LIBRARIES FLUIDSYNTH_INCLUDE_DIR)
-- Selected assembler: /usr/bin/as
-- Looking for filelength
-- Looking for filelength - not found
-- Looking for strupr
-- Looking for strupr - not found
-- Looking for stricmp
-- Looking for stricmp - not found
-- Looking for strnicmp
-- Looking for strnicmp - not found
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Performing Test HAS_VA_COPY
-- Performing Test HAS_VA_COPY - Success
-- Fluid synth libs: FLUIDSYNTH_LIBRARIES-NOTFOUND
-- Configuring done
-- Generating done
-- Build files have been written to: ~/ZDoom/relwithdebinfo


How do I go about compiling in, or compiling support for external, fluidsynth libraries? Looking at the FindFluidSynth.cmake file, I see it looks for a fluidsynth.h file, but I don't see that anywhere in the fluidsynth sources I've already downloaded.

[Edward-san]

Did you install libfluidsynth-dev?

[Virii]

Nice... that was it. Thanks.

BTW, can anyone tell me why fmod is a requirement if it doesn't actually output BGM sound in Linux?

[Blzut3]

Fmod handles all of the sounds not just the BGM.

[Vaecrius]

Anyone got a recommendation for a map editor? I really, really do not want to install WINE.

[Gez]

SLADE 3?

[Vaecrius]

...so, uh, how do I edit a map with this?

[Gez]

Actually, you shouldn't use it right now since its map editor still has several limitations and is not very stable. But it's getting there!

[Mannequin]

Didn't someone port ZETH or am I misremembering things? I seem to remember (when I used to play around with map editing) using it in a Linux environment.

-M.

[Vaecrius]

Shouldn't? There's simply no map-editing interface I can find either in the program or the documentation, in the sense of moving vertices and defining sectors and whatnot.

So far I've found Yadex and LDE which date back to 2005 and 2002 respectively. :/
ED: and neither compiles, for what appear to my untrained eyes to be use of deprecated functions.

[Mannequin]

To be honest, it's been about that long since I've done any map editing... I also seem to remember using Yadex before. I did a quick check with 'apt-get' in Mint 13 and I can only find deutex and glbsp, which aren't exactly what you're looking for.

That really sucks. If I had the time, I might make an empty promise to see about porting something.

EDIT: I've just built yadex with a few tweeks to the code. It doesn't like running in the 64 bit world:

Code: Select all • Expand view

$ ./yadex
Yadex 1.7.0 (2012-05-28)
Reading config file "/home/manny/Documents/yadex/etc/yadex.cfg".
Error: sizeof u32 is 8 (should be 4)


Now I'm thinking that there is probably a test in there somewhere for that, but I don't know if I want to dig it out and see what I can do about it... It might lead to uglier things. It may just be easier (for me) to fire up a virtual machine and install a 32 bit OS to test that the little things I did don't cause horrific trouble.

-M.

[Vaecrius]

64 bit

...yeah that probably explains what I saw. :/

Thanks for the help!

[Vaecrius]

Just did a dist-upgrade earlier in the week and finally rebooted last night to 3.2.0-0.bpo.2-amd64 and redownloading what appears to have been a corrupt NVidia driver after mistakenly running a zero-length endless DECORATE loop.

Now GZDoom gives me a black screen for a second and a half before starting. o_O

Has this happened to anyone else, or am I just having driver problems again?
(far as I can tell the driver otherwise works fine.)