Re: WDK KMDF 1.0 does not build nmake error U1065

Tech-Archive recommends: Fix windows errors by optimizing your registry

The line in the 'real' \WinDDK\3790.1830\bin\makefile.new which I believe
actually executes nmake is:

line no 3772:
MAKE_MANIFEST_CMD=nmake -nologo $(SXS_MANIFEST_OBJ1)

and acutally has a 'REAL' - minus sign 0x2D.

So I'm not so sure that is the answer.
And I don't fancy becoming an nmake expert just to fix something that should
already work - FRESH OFF THE ISO.

Although when I checked /dev/null I was surprised to find a link to a
website for Microsoft fans and lovers.


"Norman Diamond" <ndiamond@xxxxxxxxxxxxxxxx> wrote in message
news:e42RvODMGHA.3104@xxxxxxxxxxxxxxxxxxxxxxx
"Luke" <luke.evans@xxxxxxxxxxxx> wrote in message
news:ub$gKtCMGHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
Has anyone else been unable to build KMDF 1.0 driver examples?

BUILD: Adding /Y to COPYCMD so xcopy ops won't hang.
BUILD: Object root set to: ==> objchk_wnet_x86
BUILD: Compile and Link for i386
BUILD: Examining c:\winddk\wdf\kmdf10\src\kmdf directory tree for files
to
compile.
BUILD: Building generated files in
c:\winddk\wdf\kmdf10\src\kmdf\toaster\bus\static directory
errors in directory c:\winddk\wdf\kmdf10\src\kmdf\toaster\bus\static
NMAKE : fatal error U1065: invalid option '-'
BUILD: nmake.exe failed - rc = 2
etc etc etc.

Build reports 63 errors, all the same. Have followed installations
instructions to a 'T' and have made no modifications.

I reported the exact same thing to Microsoft several months ago. Their
reply can be found on any Linux system, in /dev/null.

Some time after that, I figured out that their instructions are just too
cute. When you use the mouse to copy and paste something that looks like
a
minus sign, you get something that looks like a minus sign, but
Microsoft's
programmers didn't code nmake or compilers to understand something that
looks like a minus sign. You have to type a real minus sign yourself,
from
the keyboard.

Now even after you make that adjustment, some WDK samples still don't
compile. Well they do if you figure out what ANSI code page Microsoft
tested it under, and figure out how to set your ANSI code page to the
same.
There are occasions when it would be profitable to be 7-bit clean in
writing
source code, and the WDK would be one.



.

Relevant Pages

  • Re: 10.5
    ... Minus a point to Apple for being hyper-paranoid. ... So Apple sure beats Microsoft with TimeMachine. ... but Outlook Express and Outlook have both had ...
    (comp.sys.mac.advocacy)
  • Build for Windows Mobile Failed
    ... I successfully ran configure.bat (without an architecture type as ... I ran nmake and he complaint following: ... Copyright Microsoft Corp 1988-1998. ... Opened the makefile in my editor and look up the line. ...
    (comp.lang.ruby)
  • Re: Extending ruby with c
    ... Becker ... > using nmake i get this error ... > Copyright Microsoft Corp 1988-94. ... you would need to install a C compiler. ...
    (comp.lang.ruby)
  • Re: Extending ruby with c
    ... Thank you i found nmake at ... Microsoft Program Maintenance Utility Version 1.50 ... Copyright Microsoft Corp 1988-94. ... 'cl' is not recognized as an internal or external command, ...
    (comp.lang.ruby)
  • Re: Need reviews of HLA Adventure
    ... > <RadAsm Output> ... > Microsoft Program Maintenance Utility Version 6.00.9763.0 ... > Copyright Microsoft Corp 1988-1998. ... > I'm thinking maybe I've got an old version of nmake? ...
    (alt.lang.asm)