An additional file is needed to get speex compiling properly on the Visual Studio platform. I will be submitting an updated project file in a separate, existing bug, but one of the prerequesites is that you include a missing file from the speex 1.2rc1 source.
Specifically, the file config.h from the \win32 folder in the linked download should be placed into the ioquake3 folder \libspeex along with all the other .c and .h files. I will attach this file to this bug, or you can pull it directly from the speex file. It's basically a short set of definitions.
I figure since ioq3 already includes speex, might as well include one more file related to speex!
After consultation with some blokes on the speex-dev mailing list, to get Visual Studio to compile speex as a library, you need to use config.h and the junk defined there. I did try valiantly to duplicate the ioq3 makefile's directives to get speex working like on Linux and with mingw, but I had no luck and the speex devs I talked to basically called me boneheaded for not using the config.h and related directive.
I would have used a precompiled windows library and had the user go out to get that himself, but there is none for the version that Ryan included in ioq3. So the choice was to require a VS user to download the specific version of speex used in ioq3 and generate their own libspeex.lib file, wait for speex to generate windows libraries for that specific version, compile a libspeex.lib myself and try to get that included into ioq3's SVN, OR to get the VS compile working with the included /libspeex already in ioq3. Since we're maintaining/including libspeex in ioq3 already, I figured one additional file wouldn't add too much bloat. It isn't called by any other platform but Visual Studio and enables VS to compile the included ioq3 speex, so the benefits (in my mind) seemed to greatly outweigh the bloat or inconvenience of adding an additional file.
I think including a header file is better than both including a precompiled library in ioq3 and getting the user to try and hunt down a specific version of speex to roll their own. All the other platforms "just work" for compiling ioq3 and speex and this addition allows VS to do the same.
Anyway, those are my thoughts on the subject and hopefully they are convincing enough!
config.h should be in \libspeex not in \libspeex\include\speex
In the speex-1.2rc1 tarball, it actually resides in \win32\ nowhere near any other .c or .h files, so I guess it can be put anywhere.
But it depends on if you want me to fix the path in the visual studio project file to reflect it being in \libspeex\include\speex, or if you want to just move it from there to \libspeex.
I'm good to go either way!
Created attachment 1922 [details] config.h to put into \libspeex folder Here is the file, unmodified, direct from the speex tarball.