Re: DDKBuild ISSUE with WINDDK...

From: Harry Potter (hpotter_at_azkabar.com)
Date: 10/11/04


Date: Mon, 11 Oct 2004 11:52:36 -0700

huumm... it seems that I can't attach.... how about this then...

Deleting intermediate files and output files for project 'driver - Win32
Debug'.
--------------------Configuration: driver - Win32 Debug--------------------
DDKBUILD VERSION 3.9.27 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
Comments? Suggestions? info@hollistech.com
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>VERIFY
OTHER 2>nul
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>setlocal
ENABLEEXTENSIONS
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>if
ERRORLEVEL 1 goto wrongplatform
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem some
shells is different
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
foo=dog
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>if dog
EQU cat (set foo=rat ) else (set foo=cat )
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>if cat
EQU dog goto :nt4ddkbuild
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>if /I
"-h" EQU "/?" goto usage
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem next
test, some shells is different
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>setlocal
enabledelayedexpansion
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
VAR=before
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>if
"before" == "before" (
set VAR=after
 if "!VAR!" == "after" (
rem @echo W2K or later system
 call :ddkbuild -debug -h -WNET2K checked . /a
) else (

 call :nt4ddkbuild -debug -h -WNET2K checked . /a
)
)
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>if
"-debug" == "-debug" shift
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
w2kflag=
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
================
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
NOTE: w2kflag appears to be somewhat obsolete,
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem at
best it is either null or non-null.
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
buildbsc may use its value, but the setting of
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem that
value is inconsistent.
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
================
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
chk=checked
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
fre=free
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
xp64=
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
xp2k=0
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
wnet=
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set wlh=
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
ddk=UNKNOWN
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>set
mode=
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>if "-h"
EQU "" goto usage
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>if /I -h
EQU -h goto usage
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>start
http:\\www.hollistech.com\Resources\ddkbuild\ddkbuildhelp3_9.htm
usage: ddkbuild [-debug] "TARGET" "checked | free" "directory-to-build"
[flags]
       -debug turns on script echoing for debug purposes
       TARGET can be any of the following combinations of DDK and target
platform:
       -W2K indicates development system uses W2KBASE environment
variable
                   to locate the win2000 ddk, otherwise BASEDIR is used
(optional.)
       -W2K64 indicates development syatem uses W2K64BASE environment
variable
                   to locate the win2000 64 ddk, otherwise BASEDIR is used
(optional.)
       -XP indicates development system uses XPBASE environment
variable
                   to locate the XP ddk, otherwise BASEDIR is used
(optional.)
       -XP64 indicates development system uses XPBASE environment
variable
                   to locate the XP ddk and builds IA64 binaries (optional.)
       -XPW2K indicates development system uses the XPBASE environment
variable
                   to locate the XP ddk and builds W2K binaries (optional.)
       -WNET indicates development system uses WNETBASE environment
variable
                   to locate the .Net ddk and builds .net binaries
(optional.)
       -WNETW2K indicates development system uses the WNETBASE environment
variable
                   to locate the .Net ddk and builds W2K binaries
(optional.)
       -WNETXP indicates development system uses WNETBASE environment
variable
                   to locate the .Net ddk and builds xp binaries (optional.)
       -WNET64 indicates development system uses WNETBASE environment
variable
                   to locate the .Net ddk and builds 64bit binaries
(optional.)
       -WNETA64 indicates development system uses WNETBASE environment
variable
                   to locate the .Net ddk and builds AMD 64bit binaries
(optional.)
       -WLH indicates development system uses the WHLBASE environment
variable
                   to locate the Longhorn ddk and builds Longhorn binaries
(optional.)
       -WLH64 indicates development system uses the WHLBASE environment
variable
                   to locate the Longhorn ddk and builds IA64 Longhorn
binaries (optional.)
       -WLHA64 indicates development system uses the WHLBASE environment
variable
                   to locate the Longhorn ddk and builds AMD64 Longhorn
binaries (optional.)
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo -WLHW2K indicates development system uses the WHLBASE
environment variable
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo to locate the Longhorn ddk and builds W2K binaries
(optional.)
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo.
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo -WLHXP indicates development system uses the WHLBASE
environment variable
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo to locate the Longhorn ddk and builds XP binaries
(optional.)
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo.
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo -WLHXP64 indicates development system uses the WHLBASE
environment variable
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo to locate the Longhorn ddk and builds XP IA64
binaries (optional.)
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo.
       -WLHNET indicates development system uses the WHLBASE environment
variable
                   to locate the Longhorn ddk and builds .net binaries
(optional.)
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo -WLHNET64 indicates development system uses the WHLBASE
environment variable
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo to locate the Longhorn ddk and builds IA64 .bet
binaries (optional.)
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo.
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo -WLHNETA64 indicates development system uses the WHLBASE
environment variable
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo to locate the Longhorn ddk and builds AMD64 .net
binaries (optional.)
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>rem
@echo.
       checked indicates a checked build.
       free indicates a free build (must choose one or the other of
free or checked.)
       directory path to build directory, try . (cwd).
       flags any random flags or arguments you think should be passed
to build (note that the
                   visual studio /a for clean build is translated to the
equivalent build flag.)
     Note also that multiple arguments can be specified by using quotes to
contain
     the set of arguments, as in "-Z foo blortz w2k xp"

        ex: ddkbuild -XP checked .
        NOTE: windows .net DDK versions supported must be build 3663 or
later
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>goto
:EOF
C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>goto
:EOF

Passthru.sys - 0 error(s), 0 warning(s)



Relevant Pages

  • Re: DDKBuild ISSUE with WINDDK...
    ... ERRORLEVEL 1 goto wrongplatform ... EQU dog goto:nt4ddkbuild ... rem @echo W2K or later system ... binaries ...
    (microsoft.public.vc.debugger)
  • Re: DDKBuild ISSUE with WINDDK...
    ... ERRORLEVEL 1 goto wrongplatform ... EQU dog goto:nt4ddkbuild ... rem @echo W2K or later system ... binaries ...
    (microsoft.public.development.device.drivers)
  • a turbo assembly language
    ... if not exist %1.m goto pst1_n_as2 ... echo Uso con la shell: ... int catstr ... õ2\nmov õ1, eax"); ...
    (alt.lang.asm)
  • Re: Question for ¬a/b
    ... if not exist %1.m goto pst1_n_as2 ... echo Uso con la shell: ... char* estrai ... int catstr ...
    (alt.lang.asm)
  • Re: robocopy validation
    ... Robocopy did not copy any files. ... if errorlevel 8 echo **FAILED COPIES** & goto end ...
    (microsoft.public.win2000.general)

Quantcast