DDKBUILD VERSION 3.13 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS


Comments? Suggestions? info@hollistech.com


usage: ddkbuild [-debug|-verbose] "TARGET" [-prefast|-drvfast|-cuv] "checked | free" "directory" [flags]

Script Flags Group
-debug turns on script echoing for debug purposes
-verbose announce various script activities to stdout
-quiet quiet mode: only errors and warnings sent to stdout
TARGET Group can be any of the following combinations of DDK version and platform OS:
   -W2K indicates development system uses W2KBASE environment variable to locate the win2000 ddk, otherwise BASEDIR is used (optional.)
  -W2K64 indicates development system 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 Beta.)
  -WLH64 indicates development system uses the WHLBASE environment variable to locate the Longhorn ddk and builds IA64 Longhorn binaries (optional Beta.)
  -WLHA64 indicates development system uses the WHLBASE environment variable to locate the Longhorn ddk and builds AMD64 Longhorn binaries (optional. Beta)
  -WLHNET indicates development system uses the WHLBASE environment variable to locate the Longhorn ddk and builds .net binaries (optional. Beta)
  -WDF indicates development system uses the WDF_DDK and WDF_ROOT environment variables to locate the WDF supported DDK and build a W2K3 (.net) binary (optional Beta) .
  -WDFXP indicates development system uses the WDF_DDK and WDF_ROOT environment variables to locate the WDF supported DDK and build an XP binary (optional Beta) .
  -WDFW2K indicates development system uses the WDF_DDK and WDF_ROOT environment variables to locate the WDF supported DDK and build an XP binary (optional Beta) .
  -WDF64 indicates development system uses the WDF_DDK and WDF_ROOT environment variables to locate the WDF supported DDK and build an XP binary (optional Beta) .
  -WDFA64 indicates development system uses the WDF_DDK and WDF_ROOT environment variables to locate the WDF supported DDK and build an XP binary (optional Beta) .
Special Build Options Group
-prefast run prefast rather than a normal build. If queit mode is selected prefast errors and warnings go to stdout. Otherwise the prefast gui is invoked. The prefast log file is directed to the target directory file prefast.xml
-drvfast run the driver fast version of prefast (only if the ddk supports it)
-cuv build the driver using CUV (see ddk docs)
Build Type Group
checked indicates a checked build.
free indicates a free build (must choose one or the other of free or checked.)
Location Group
directory path to driver source directory. Try . (cwd).
Build Flags Group
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"

Example 1: ddkbuild -XP checked .

builds the component in the current directory using the XP ddk located by the environment variable XPBASE for the XP platform. A checked component will be built.

Example 2: ddkbuild -WNET -cuv checked src -cZ

builds the component located in the src directory using the Windows 2003 ddk located by the environment variable WNETBASE. The DDK CUV option is selected, a checked build will be run, and the "-cZ" flags will be passed to build, resulting in a clean build of all modules.

Example 3: ddkbuild -WDFXP -drvfast free  . -cZ

builds the component located in the current directory using the WDF compatible DDK located by the WDF_DDK environment variable and the WDF kit located by WDF_ROOT. The drvfast settings for prefast are used to invoke a prefast build of the components. A free version of the components will be built, and build will be passed the "-cZ" flags, resulting in a clean build of all modules.

Note that the position of the various groups of options are important.