The problem is ... anything that I could compile, I could test myself, and any port where I need testing, I cannot compile.
Also, I do not know which OS you have, or which optional libraries
you might have. There is also a file of compile options that could be
customized (doomdefs.h, ... I have been working on something else and cannot remember the exact name right now).
Do you have any gcc compiler installed at all ??
That is the hardest prerequisite to satisfy. I have been testing with gcc 3.6, gcc 4.3, on Linux. I will have MinGW setup again on Win98 soon. I cannot compile for any newer Windows version.
This is where I really need help from users who can compile on the newer Windows.
The second problem is installing SDL, and you still need to do that even with a precompiled binary, unless you intend to test one of the non-SDL port options.
To compile the only commands needed are.
Edit make_options for you desired port, according to the instructions in the Makefile, then ..
Also, there are already some fixes, so get latest SVN version.
That is probably the 3nd hardest thing to accomplish.
Perhaps if you post the necessary information, there might be some other reader willing to compile it.
Also, within a week or so, this will get released as alpha5. I was hoping to find any bugs concerning the Windows compile before then.
But you could wait for that version to be released.
Thank you for your interest ...
There is no installer yet, mostly because there is no predetermined installation location.
Generally, you copy everything in ../bin to your running directory, put in the legacy.wad file. You also might add a WAD, or configure DOOMWADDIR env var.
I am curious to how users set up their running directory for Doom ports.
There does not seem to be any predictable organization.
On Linux, I might consider putting a DoomLegacy directory in
but what do Windows users do ...
Adding entries to the menus is a OS version dependent exercise that is rarely to the users liking.
Last edited by wesleyjohnson on 12-26-13 at 20:46