------------------
System Information
------------------
Time of this report: 1/30/2011, 20:16:01
Machine name: CENTURION
Operating System: Windows 7 Home Premium 32-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 05/22/09 14:07:10 Ver: 08.00.14
Processor: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz (2 CPUs), ~3.0GHz
Memory: 2048MB RAM
Available OS Memory: 2048MB RAM
Page File: 1838MB used, 2256MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode
Any ideas? I tried the wiki and tried Google. No luck. If you need any more information than that, let me know. Thanks.
It looks like arith.h failed to be generated. Try manually compiling arithchk.c and running it. If some C code is printed to the console instead of to arith.h, just copy what was printed and paste it in arith.h.
Go to the command prompt, set the current directory to the containing folder (type "cd "<path to ZDoom source>\gdtoa"" minus the outer quotes), and type "gcc arithchk.c". That will compile the file and generate the file "a.exe". Run it. This will generate arith.h or, as mentioned above, print the expected contents to the standard output stream (the command prompt). Once you have arith.h, try compiling ZDoom again.
When I first tried compiling ZDoom, this exact same thing happened to me. I guess ZDoom just hates MinGW.
I still haven't successfully compiled ZDoom. Last time I tried, I got most of the way when one of the included projects wouldn't compile for no apparent reason.
C:\Users\Cleveland Rock\Source Code\gzdoom\release>cd ..\gdtoa
C:\Users\Cleveland Rock\Source Code\gzdoom\gdtoa>gcc dmisc.c
In file included from dmisc.c:32:0:
gdtoaimp.h:192:21: fatal error: gd_qnan.h: No such file or directory
compilation terminated.
C:\Users\Cleveland Rock\Source Code\gzdoom\gdtoa>
Argh! I don't know what I'm doing wrong. I've compiled GZDoom before. The last time I tried was r2256, which compiled successfully.
…Wait, r2256? How can that be? The most recent revision, the one I'm trying to compile, is 1186.
Cleveland Rock wrote:I guess I should compile this file manually, too?
Yes, you should do that one manually, too. As far as I remember, that's the only other one you'll need to do this for.
Cleveland Rock wrote:Argh! I don't know what I'm doing wrong. I've compiled GZDoom before. The last time I tried was r2256, which compiled successfully.
…Wait, r2256? How can that be? The most recent revision, the one I'm trying to compile, is 1186.
Well, you might have compiled ZDoom r2256, which was committed some time ago.
C:\Users\Cleveland Rock\Source Code\gzdoom\release>cd ..\gdtoa
C:\Users\Cleveland Rock\Source Code\gzdoom\gdtoa>gcc dmisc.c
In file included from dmisc.c:32:0:
gdtoaimp.h:192:21: fatal error: gd_qnan.h: No such file or directory
compilation terminated.
C:\Users\Cleveland Rock\Source Code\gzdoom\gdtoa>
I've been using CMake to generate a MinGW makefile, since one doesn't appear to be provided with the GZDoom source code. Is there something else I could be doing?
Aside from using Visual C++ I don't have an idea. I don't know how many people actually use MinGW to compile ZDoom or GZDoom but it's probably not many.
Well, I really don't feel like downloading an old version just so I can compile this, so, unless someone writes a tutorial for compiling it with Visual C++ 2010 Express, I'm just not gonna bother compiling it. Sigh. If I didn't require so many Windows-specific programs (Doom Builder, for example), I'd go back to Linux. Compiling stuff was so easy on Linux.
I think you should be able to use the Wiki guide for VC 2005 with VC 2010. I know VC 2010 will have no trouble converting the solution and project files to its version, and the steps should be the same; though the exact place of stuff in the options and properties menus will have changed.
IIRC, the main difference is that in VC 2010, paths (for libraries, includes, exes, etc.) are project-dependent rather than global.