[r1023] MinGW Compiling Error

Discuss anything ZDoom-related that doesn't fall into one of the other categories.
Post Reply
User avatar
Cheeseball
Posts: 45
Joined: Mon Dec 17, 2007 6:58 pm
Location: Philippines
Contact:

[r1023] MinGW Compiling Error

Post by Cheeseball »

Just tried to compile the latest svn version using MinGW...

Using:
svn 1023 (clean, direct from trunk)
gcc core 4.21
gcc g++ 4.21
FMOD Ex Programmers API 4.16.00

Getting this particular error with fmodsound.cpp:

Code: Select all

Compiling fmodsound.cpp:                                              [ERROR]
g++ -fno-strict-aliasing -DWIN32 -D_WIN32 -D_WINDOWS -DHAVE_STRUPR -DHAVE_FILELE
NGTH -DI_DO_NOT_LIKE_BIG_DOWNLOADS -D__forceinline=inline -MMD -Izlib -IFLAC -Ij
peg-6b -Isrc -Isrc/win32 -Isrc/g_doom -Isrc/g_heretic -Isrc/g_hexen -Isrc/g_rave
n -Isrc/g_strife -Isrc/g_shared -Isrc/oplsynth -Isrc/sound -Isrc/textures -Isrc/
thingdef -Isnes_spc/snes_spc -I"c:/program files/FMOD SoundSystem/FMOD Programme
rs API Win32"/api/inc -DNDEBUG -march=pentium -mtune=i686 -Wall -Wno-unused -O2
-fomit-frame-pointer -pipe -ffunction-sections -fno-rtti -DUSEASM=1 -o releaseob
j/fmodsound.o -c src/sound/fmodsound.cpp
================================================================================
In file included from src/sound/fmodsound.h:5,
                 from src/sound/fmodsound.cpp:50:
c:/program files/FMOD SoundSystem/FMOD Programmers API Win32/api/inc/fmod.h: In
function 'FMOD_RESULT FMOD::Memory_Initialize(void*, int, void* (*)(unsigned int
, FMOD_MEMORY_TYPE), void* (*)(void*, unsigned int, FMOD_MEMORY_TYPE), void (*)(
void*, FMOD_MEMORY_TYPE))':
c:/program files/FMOD SoundSystem/FMOD Programmers API Win32/api/inc/fmod.h:1761
: error: too few arguments to function 'FMOD_RESULT FMOD_Memory_Initialize(void*
, int, void* (*)(unsigned int, FMOD_MEMORY_TYPE), void* (*)(void*, unsigned int,
 FMOD_MEMORY_TYPE), void (*)(void*, FMOD_MEMORY_TYPE), FMOD_MEMORY_TYPE)'
src/sound/fmod_wrap.h:49: error: at this point in file
src/sound/fmod_wrap.h: In member function 'FMOD_RESULT FMOD::System::setCallback
(FMOD_SYSTEM_CALLBACKTYPE, FMOD_RESULT (*)(FMOD_SYSTEM*, FMOD_SYSTEM_CALLBACKTYP
E, void*, void*))':
src/sound/fmod_wrap.h:96: error: cannot convert 'FMOD_SYSTEM_CALLBACKTYPE' to 'F
MOD_RESULT (*)(FMOD_SYSTEM*, FMOD_SYSTEM_CALLBACKTYPE, void*, void*)' for argume
nt '2' to 'FMOD_RESULT FMOD_System_SetCallback(FMOD_SYSTEM*, FMOD_RESULT (*)(FMO
D_SYSTEM*, FMOD_SYSTEM_CALLBACKTYPE, void*, void*))'
mingw32-make[1]: *** [releaseobj/fmodsound.o] Error 1
mingw32-make[1]: Leaving directory `C:/zdsrc'
mingw32-make: *** [game] Error 2
Any ideas? I can compile stable 2.2.0 fine (with fmod 3.75, of course). :oops:
User avatar
Cheeseball
Posts: 45
Joined: Mon Dec 17, 2007 6:58 pm
Location: Philippines
Contact:

Re: [r1023] MinGW Compiling Error

Post by Cheeseball »

I just updated to r1024. Of course, it still doesn't work. :?

I think the latest stable version of FMOD Ex (4.16.00) might be causing this issue. I'll try to compile again with an older version and see what happens...
User avatar
Cheeseball
Posts: 45
Joined: Mon Dec 17, 2007 6:58 pm
Location: Philippines
Contact:

Re: [r1023] MinGW Compiling Error

Post by Cheeseball »

Guu... no one knows any solution? I just tried earlier versions of FMOD Ex and it still gives the same error... :(
User avatar
randi
Site Admin
Posts: 7749
Joined: Wed Jul 09, 2003 10:30 pm
Contact:

Re: [r1023] MinGW Compiling Error

Post by randi »

If you use FMOD Ex 4.14.0x, it will be fine, since that's what it was compiled with. The error you get when compiling with 4.16 is because one function received an extra argument, and the wrapper hasn't been updated for it.

But you should avoid 4.16.00 for now anyway.
User avatar
Cheeseball
Posts: 45
Joined: Mon Dec 17, 2007 6:58 pm
Location: Philippines
Contact:

Re: [r1023] MinGW Compiling Error

Post by Cheeseball »

Wait, so 4.16.00 does not allow access to audio hardware for playback of .mod, .s3m, .xm, .it, and .mid formats?

That sucks. :shock:

I haven't tried 4.14.08 yet, but 4.15.06 gives the same issue, as does 4.17.00.
Post Reply

Return to “General”