What is the error that is causing the header file to barf when using MASM?
Extending the make/build is possible using the makefile.inc as Martin
suggested, but the question then is will Link be happy with the obj file?
The best bet is to “fix” the header file and stay within the realm of tools
that are known to work when building drivers.
And really, what is so “special” about that “optimized” code? I remember
when it was common practice to write your code in PASCAL, FORTRAN, or even
C, generate ASM files and then butcher the living hell out of them to get
the final executable to fit in that 16K of RAM in which you had to run.
That’s how the boys and girls at Apple got the first Macintosh to fit in
it’s original 64k. “Optimized” code to day? Can you spell “bullshit”? I’ll
bet it’s the “pet code” of some arrogant developer who thinks his shit don’t
stink and more than likely it is now done better in the OS or exsiting
support libs
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of NCH Obble Smith
Sent: Monday, November 23, 2009 10:39 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] nasm compiled asm files
Hello everyone,
Is it possible to set the sources file to compile an asm file with nasm
instead of masm?
Problem:
I have a customer that insists of having 32bit asm “optimized” code a
driver and it’s compiler is nasm.
When I finally got the thing to compile for i386 base files, I am
getting errors about the .h file, but not when i compile with nasm.
So is it possible to tell build to use nasm instead of masm?
Cheers
Obble.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
__________ Information from ESET Smart Security, version of virus signature
database 4633 (20091124) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 4633 (20091124) __________
The message was checked by ESET Smart Security.
http://www.eset.com