🚀 go-pugleaf

"Stoltenberg Family" <ji...@flash.net> schrieb im Newsbeitrag
news:39ADDF86.BFDB4DB1@flash.net...
> Hey, I've messed with the d2 source.  And I have a question.  How would
> it be possible for me to port it so that I could compile it using VC6?
> That is the only compiler I have and I don't feel like having to learn
> to use another one.
>

Sorry to tell you, but it is quite impossible. I once tried with D2/VC5.
It's mainly three reasons:
* chaos. Without any insight in the "organization" (if one call it that) of
the code you often don't know what this special function/module is supposed
to do. And you need to know that if the compiler complains this is incorrect
code or something. D2 ist not much better than D1, it contains of a lot of
dirty hacks. Maybe a little bit of support from PX Software would help.
* Watcom dependencies. The Descent 1/2 engine is heavily dependant on the
Watcom compiler. It uses tons of special #pragmas, inline assembly etc.
You'd need at least a "compatible" compiler. I heard it was possible to use
DJGPP for the DOS version, but that won't help for OpenGL / D3D builds.
* Descent 1 legacy. It also employs pure assembly and - in at least one
point of the renderloop - even self-modifying code. That doesn't make things
easier. Remaining DOS stuff and special cases for the accelerated DOS
versions (e.g. for the ViRGE and 3Dfx chipsets) is to be found and removed.

To sum it up: You need someone from PX who was involved in the development
to help you and a staff of experienced C / assembler coders. Or _at least_ a
Watcom compiler. And much spare time. I didn't get too far. The error
handling system worked (cool!) and a window opened showing the D2 loading
screen. That all with sound / network / joystick code commented out and
nearly the complete 3D engine missing. Then, when you expect the pilot
selection window to come up, the thing crashes and I don't know why.

--
sk