BINS_DDK.exe
-
- InsideQC Staff
- Posts: 1120
- Joined: Sat Oct 16, 2004 3:34 pm
Microsoft's Driver Developer Kit binaries. Which is any easy way to get MASM, Microsoft's assembler, which is needed to build the Quake engine source without switching off the assembler code. (most GLQuake projects switch off the assembly because it's not that much of a speed advantage in non-software).
thanks. i have been looking for this
http://bradshub.ath.cx - take a look at my web site.
Come on, admit it. You're the smartest person you know.
Come on, admit it. You're the smartest person you know.
-
- Posts: 368
- Joined: Thu Jun 25, 2009 4:45 am
- Location: Michigan
Re: BINS_DDK.exe
even if you're not doing a software engine, I still recommend using the MASM stuff when available, because of sound mixing, this applies just as well to GLQuake
i should not be here
Re: BINS_DDK.exe
theres also http://www.masm32.com/ and its still being updated as well
Productivity is a state of mind.
Re: BINS_DDK.exe
You don't need MASM if you're compiling with Visual C++ 2008 or 2010 (don't know about 2005) - it comes with the download already (even the express versions).
Personally I just GAS2MASM the files, pull the resulting .asm files from the output folder, include them in the project (selecting the appropriate build rule when prompted) and junk the .s files entirely. There's a bit of massaging needed for some of the software Quake stuff where some jump labels have the same name aside from case, but otherwise it's clean.
Quake II used inline ASM in it's software renderer which might be worth looking at/copying from (I reckon that if you're using MASM in the first place then the added portability is low on your priority list).
Personally I just GAS2MASM the files, pull the resulting .asm files from the output folder, include them in the project (selecting the appropriate build rule when prompted) and junk the .s files entirely. There's a bit of massaging needed for some of the software Quake stuff where some jump labels have the same name aside from case, but otherwise it's clean.
Quake II used inline ASM in it's software renderer which might be worth looking at/copying from (I reckon that if you're using MASM in the first place then the added portability is low on your priority list).
We had the power, we had the space, we had a sense of time and place
We knew the words, we knew the score, we knew what we were fighting for
We knew the words, we knew the score, we knew what we were fighting for
Re: BINS_DDK.exe
msvc gives up on optimisations within any function that contains a little asm, so if you use inline assembler, make sure its isolated within its own functions.
msvc doesn't support inline assember for the amd64 instruction set at all. and even if it did, you'd need to rewrite it all anyway. Its not just register names/sizes.
msvc doesn't support inline assember for the amd64 instruction set at all. and even if it did, you'd need to rewrite it all anyway. Its not just register names/sizes.
Re: BINS_DDK.exe
an alternative is jwasm (port of the watcom assembler) it has close syntax to the old masm.
from jwasms site.
native support for output formats Intel OMF, MS Coff (32- and 64-bit), Elf (32-and 64-bit), Bin and DOS MZ.
64 bit inline assembly might be possible with the intel compiler hooked up to msvc cant remember though.
from jwasms site.
native support for output formats Intel OMF, MS Coff (32- and 64-bit), Elf (32-and 64-bit), Bin and DOS MZ.
64 bit inline assembly might be possible with the intel compiler hooked up to msvc cant remember though.
Productivity is a state of mind.