Could Chocolate Doom builds be added?

Discuss the hosted development builds here.
[Home]

Moderator: Dev Builds Team

User avatar
Janizdreg
Posts: 8
Joined: Fri Oct 07, 2005 18:41
Location: Finland
Contact:

Could Chocolate Doom builds be added?

Post by Janizdreg »

The current situation with the Chocolate Doom SVN builds is that exp(x), the current maintainer, has become unable to maintain his builds. Which means we are now hoping someone from the DRD Team SVN builds team could do it. So, would anyone be willing to do this?

Also, in case it helps, the script exp(x) used to build the Chocolate SVN builds is available here. The build process was fully automated, so maybe you could make it that way too.

In addition to the mainline stuff, there are currently several different Chocolate branches in the works: an OPL branch, a Raven (Heretic/Hexen) branch and a Strife branch. If builds of all of these could be made, it would be excellent.
User avatar
Rachael
Developer
Developer
Posts: 3646
Joined: Sat May 13, 2006 10:30

Re: Could Chocolate Doom builds be added?

Post by Rachael »

This is a possibility, but the basic prerequisite to offering such builds would be a volunteer who would be willing to maintain them. If someone does offer to compile them and check regularly for updates, we might be able to host them.
User avatar
Gez
Developer
Developer
Posts: 1399
Joined: Mon Oct 22, 2007 16:47

Re: Could Chocolate Doom builds be added?

Post by Gez »

I've taken a look, since I already have all the needed libraries installed, as they're also required by Eternity. I make no promise, however. I need to set it up so that I have only the trunk and the branches, and that they all form just one project; because I don't want to bother with the tags and the miscellaneous stuff, nor to have to compile each branch separately. (And I don't feel like installing Bash and mingw for Windows, so exp(x)'s script is useless for me.) For the moment, it refuses to compile with the following errors:

Code: Select all

1>MSVCRTD.lib(cinitexe.obj) : warning LNK4098: defaultlib 'msvcrt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library
1>d_iwad.obj : error LNK2019: unresolved external symbol __imp__RegCloseKey@4 referenced in function _GetRegistryString
1>d_iwad.obj : error LNK2019: unresolved external symbol __imp__RegQueryValueExA@24 referenced in function _GetRegistryString
1>d_iwad.obj : error LNK2019: unresolved external symbol __imp__RegOpenKeyExA@20 referenced in function _GetRegistryString
1>i_system.obj : error LNK2019: unresolved external symbol __imp__MessageBoxW@16 referenced in function _I_Error
Probably very easy to fix, I'll look more into it later.
User avatar
Gez
Developer
Developer
Posts: 1399
Joined: Mon Oct 22, 2007 16:47

Re: Could Chocolate Doom builds be added?

Post by Gez »

Okay, so to get rid of the conflict: Project Properties->Linker->Input->Ignore specific libraries: msvcrt
To solve the external symbols: Project Settings->Linker->Input->Additional dependencies: advapi32.lib user32.lib SDL.lib SDL_mixer.lib SDL_net.lib SDLmain.lib

Now Doom and OPL compile. Though there are still a lot of warnings about sloppy coding (mostly unary minus operators).

However, Chocolate Raven doesn't compile. Basically, it whines about config.h and inttypes.h. Further, there is no project file for Chocolate Strife yet. Finally, Setup and Server only have project files for the Raven and Strife branch; if I compile them I'd prefer to compile those from the trunk.

Solved by adding additional include dirs to the projects; however now it fails because of this:
fatal error RC1110: could not open .\win32.rc
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Re: Could Chocolate Doom builds be added?

Post by Graf Zahl »

Since Fraggle doesn' use MSVC I'm not surprised that these files are not well maintained...
User avatar
Gez
Developer
Developer
Posts: 1399
Joined: Mon Oct 22, 2007 16:47

Re: Could Chocolate Doom builds be added?

Post by Gez »

I changed the configuration to "release" instead of "debug", and it's now even worse. ;)
Spoiler:

I think I'll leave it be for the time being. This obviously should be done by someone who has a Linux/bash/mingw setup for compiling.
Post Reply

Return to “Development Builds”