C:\PROGRA~1\COMPUW~1\DRIVER~1\DRIVER~4\source>build.exe -ceZ
BUILD: Object root set to: ==> objchk
BUILD: Adding /Y to COPYCMD so xcopy ops won't hang.
BUILD: /i switch ignored
BUILD: Compile and Link for i386
BUILD: Examining c:\progra~1\compuw~1\driver~1\driver~4\source directory for files to compile.
c:\progra~1\compuw~1\driver~1\driver~4\source
BUILD: Compiling c:\progra~1\compuw~1\driver~1\driver~4\source directory
Compiling - k1394.cpp for i386
Compiling - k1394async.cpp for i386
Compiling - k1394isoc.cpp for i386
Compiling - kevent.cpp for i386
Compiling - klower.cpp for i386
Compiling - kmutex.cpp for i386
Compiling - kpnplow.cpp for i386
Compiling - ksemaphr.cpp for i386
Compiling - kspin.cpp for i386
Compiling - ksysthrd.cpp for i386
Compiling - ktimer.cpp for i386
Compiling - kusb.cpp for i386
Compiling - kustring.cpp for i386
Compiling - util.cpp for i386
Building Library - c:\progra~1\compuware\driverstudio\driverworks\lib\i386\kndiswdm.lib for i386
lib() : error LNK1181: cannot open input file 'objchk\i386\kusb.obj'
BUILD: Done
28 files compiled
1 library built - 1 Error
Errors in the build process. Cannot copy build result to DriverWorks\lib.
Method 1 – Using the Microsoft Visual C++ build commands from within Microsoft Visual Studio.
This is the most convenient method, but it does not use the BUILD utility supplied by Microsoft. We recommend that you use this method while you are actively developing your driver, but that you use the BUILD program to build the final production release of your driver.
Method 2 – Using the DriverStudio Build with BUILD.EXE command from within Microsoft Visual Studio.
This is a convenient way to use the DDK BUILD utility in conjunction with the SOURCES file and MAKEFILE from within Visual Studio.
Method 3 – Using command line build scripts with SOURCES files and the DDK BUILD utility.
就是使用2 3两种方式都不能编译，多谢帮忙！
