Trouble compiling SDL-Doom.

[Adam Oker]

So,i wanted to compile doom's source code for leaning purposes. However, the problem is, doom's source code is meant to run Linux, and i'm too broke to afford Linux (my pc's storage is on the weak side). So i decided to compile the next best thing, SDL Doom!

So i got SDL 1.0, set it up on Code::Blocks and tried to compile, however it throws this error on m_misc.c, lines 260 to 269 (nice) get the same error  :

 

So, does anyone know what could be causing the error?

Thanks!

[Shepardus]

Any particular reason why SDL Doom rather than a port that's actively maintained like Chocolate Doom, Crispy Doom, dsda-doom, Woof, GZDoom, etc.? SDL Doom is ancient and I'll be surprised if you can build it for a modern system without making significant updates to it. The ones I mentioned have documented build instructions for Windows which I assume you're using (Chocolate Doom, Crispy Doom, dsda-doom, Woof, GZDoom), and since people actually work on them you can rest assured that there are others who are able to successfully build and who may be able to help you if you run into problems with the instructions.

[Adam Oker]

5 hours ago, Shepardus said:

Any particular reason why SDL Doom rather than a port that's actively maintained like Chocolate Doom, Crispy Doom, dsda-doom, Woof, GZDoom, etc.? SDL Doom is ancient and I'll be surprised if you can build it for a modern system without making significant updates to it. The ones I mentioned have documented build instructions for Windows which I assume you're using (Chocolate Doom, Crispy Doom, dsda-doom, Woof, GZDoom), and since people actually work on them you can rest assured that there are others who are able to successfully build and who may be able to help you if you run into problems with the instructions.

Well, i kinda tried to avoid source ports because they have feature that are somewhat complicated, and i wanted to mess around with something close to the original basic Linux Doom.

[Shepardus]

1 hour ago, Adam Oker said:

Well, i kinda tried to avoid source ports because they have feature that are somewhat complicated, and i wanted to mess around with something close to the original basic Linux Doom.

SDL Doom is a source port too. If you want something close to the original, then you should look at Chocolate Doom, as the point of that source port is to reproduce the original game but for modern systems.

[Adam Oker]

1 minute ago, Shepardus said:

SDL Doom is a source port too. If you want something close to the original, then you should look at Chocolate Doom, as the point of that source port is to reproduce the original game but for modern systems.

Alright, i tried following the Chocolate Doom guide on how to build for windows, but i'm having an issue with the autogen step.

I get this error :

I downloaded the dependencies, and i wrote the command on the mingw32.exe.

So....help?

 

[Adam Oker]

(the reply got resubmitted,idk why)

Edited April 8, 2024 by Adam Oker
oop

[wesleyjohnson]

I run Linux, Slackware.  You can get Linux for free from most of the distributions.  I know that Slackware allows free downloads from its site.  You can also download the image for a Knoppix Linux CDROM that you can boot Linux and run it entirely from the CDROM, which allows to you use and fix the hard drive (it is a rescue CDROM).

 

For the above, you have to have autogen installed.  This is a standard for GNU compiler on Linux.  The installation for MINGW tends to be in sections as MINGW is just the compiler.  I am not sure on autogen, as the DoomLegacy port does not use autogen.

 

If you want to compile a Doom using Mingw, then I know that DoomLegacy will work, as I compile that using Mingw on a WinXP system.

DoomLegacy has got many advanced features and many bug fixes, but it also has a config file, where you can disable all the features you do not want (at compile - time).  DoomLegacy does have trouble with some old demos due to the way they require exact execution in order to stay in sync, but that does not affect playing any games.   I believe that DoomLegacy is related to SDL_Doom.

The requirements for compiling DoomLegacy are very low, as it stays with the minimal tool set.  It only requires SDL, and can be compiled for SDL1 or SDL2.

 

A Mingw installation has two make programs, one is installed with the base system, and one comes the Mingw compiler.  You probably have to use the Mingw32-make.

You have to use the mingw make, as the default make is not compatible with our Makefile and probably not with most other complicated make files.:

>> mingw32-make

 

If you go with too old of a port, then you will not get the many bug fixes that have been discovered over the many years of support.

Many of the newer, larger, wads, require the bug fixes, and many others require some of the advanced features, like block map expansion, and DeePsea, and others.

 

Edited April 22, 2024 by wesleyjohnson