Helixhorned, on 05 November 2012 - 04:48 AM, said:
TerminX, on 05 November 2012 - 08:32 AM, said:
Done:
r3274 said:
I also added support for building 64-bit Windows executables. We are not planning on distributing packages containing 64-bit exes, but they may be of some use.
At present, 64-bit builds have some drawbacks:
DirectInput is broken--this means that you will get an error if you have a joystick plugged in at runtime. Mouse and keyboard are unaffected.Fixed.ebacktrace needs special attention to be ported to work with the structure of 64-bit executables.FIxed.- The classic renderer will be measurably slower compared to 32-bit builds because Ken's ultrafast ASM code is 32-bit, forcing other architectures to use the slower C ports of the code. This is the only truly endemic drawback and is unlikely to be resolved anytime soon.
If you are interested, you can take a look at the updated build instructions. If there is enough interest, I could post some 64-bit binaries for the curious, but not regularly.
On a related note, the 32-bit build setup has been simplified because the DirectX headers and import libraries are completely self-contained now, no longer an external dependency.

Help
Duke4.net
DNF #1
Duke 3D #1



