The dirs file specifies which directories in the subtrees contain source code files that are to be built. The sources file specifies which source files are required to build the current driver.
If your driver will consist of multiple binaries, or the source will be kept in multiple directories, you may need to create a dirs file specifying which directories are to be built and in what order. Each separate binary will require a sources file describing which files are to be compiled/linked to create the driver.
Each driver directory also contains a makefile. As build spawns the nmake utility for each source file listed in sources, nmake uses the makefile to generate dependency and command lists. The standard makefile in a driver source code directory directs nmake to the master nmake macro definition file, makefile.def. This file defines the flags for the build tools such as the compiler and linker. Makefile.def simplifies the creation of platform-independent driver projects and is similar to the ntwin32.mak file in the Win32 SDK.
Once you have your dirs, sources and makefile files created, the next step is to run build. Build will parse the sources file and spawn nmake for each source file. Nmake will evaluate the macros in makefile.def and spawn the C compiler with the proper switches. After the compile stages are completed, build will spawn nmake again to link the objects and complete the driver building phase.
If your sources file is correct, running build is all that is required to compile and link your driver. Using build and makefile.def removes the guesswork from such things as which compiler switches are required, and what arguments the linker requires. By adding the appropriate defines to the sources file, it is possible to control the build options in a platform-independent fashion.
During driver development you will need to build free and checked versions of your driver. This is controlled by environment variable settings which are interpreted by build and nmake. These variables are set by setenv.bat, as discussed previously. To build a free driver, run build from the free environment. To build a checked driver, run build from the checked environment.
Template files (.tpl) for dirs, sources, makefile, and other files can be found in the \destination\doc directory. Working versions of these files can be found in driver source subdirectories of the DDK. Examining these files along with makefile.def (located in the \destination\inc directory) will provide additional information.
For more information about the build utility, see the Windows 2000 Programmer's Guide.
set path=%path%;c:\msdev\bin set include=%include%;c:\msdev\include set lib=%lib%;c:\msdev\libThen switch to c:\ddk\src\print\ and select the driver to build.
To build, simply type BLD. Note: You may need to run BLD from psprint first.
Logs are in build.log and build.wrn.
Output .dll products are in c:\ddk\lib\i386 unless otherwise noted in build.log.
Create and switch to c:\ddk\src\print\newdrv
Type cd newdrv
Type xcopy \ddk\src\print\textonly\*.* ..\newdrv /s
To build, simply type bld. Note: You may need to run BLD from psprint first.
Logs are in build.log and build.wrn.
Output .dll products are in c:\ddk\lib\i386 unless otherwise noted in build.log.
The dirs file specifies which directories in the subtrees contain source-code files which are to be built. The sources file specifies which source files are required to build the current driver.
If your driver will consist of multiple binaries, or the source will be kept in multiple directories, you may need to create a dirs file specifying which directories are to be built and in what order. Each separate binary will require a sources file describing which files are to be compiled/linked to create the driver.
E-mail ntwish@microsoft.com with product suggestions.http://www.microsoft.com/hwdev (For hardware developers only.)
http://www.microsoft.com/support/products/developer/ddk_hardware/ (For device driver writers only.)
Newsgroups at msnews.microsoft.com include:
microsoft.public.win32.programmer.kernel (Microsoft Windows 95 and Microsoft Windows NT® driver/kernel programming
microsoft.public.win16.programmer.kernel (Legacy Windows driver programming)
microsoft.public.usasalesinfo.developer.sdk-ddk (SDK- and DDK-related information.)
comp.os.ms-windows.programmer.nt.kernel-mode (Development of Windows NT kernel-mode drivers.)
Other competitive device driver developer houses include:
http://www.bhs.com (Beverly Hills Software—Windows NT Resource Center) http://www.blackice.sendfax.com (Black Ice Software) http://www.bluewatersystems.com (Blue Water Systems) http://www.chsw.com (Cherry Hill Software) http://www.ntinternals.com (NT Internals) http://www.numega.com (Nu-Mega Technologies) http://www.vireo.com (Vireo software—Driver Wizards) http://www.tetradyne.com (Tetradyne Software)
Windows NT Workstation Resource Kit, Microsoft Press (ISBN: 1-57231-343-9) Inside Windows NT, by Helen Custer, Microsoft Press (ISBN: 1-55615-481-X) Inside the Windows NT File System, by Helen Custer, Microsoft Press (ISBN: 1-55615-660-X) The Windows Device Driver Book, by Art Baker, Prentice Hall (ISBN: 0-13-184474-1) Windows NT DDK Graphics Device Driver Development/Design Guide and Reference (Windows NT DDK) Advanced Windows NT, by Jeffrey Richter, Microsoft Press (ISBN: 1-55615-567-0) Microsoft Windows NT Server Resource Kit by Microsoft Corporation, 1995 (ISBN: 1-57231-344-7) Microsoft Windows NT Workstation Resource Kit by Microsoft Corporation, 1995 (ISBN:1-57231-343-9) Advanced Windows (with CD-ROM) by Jeffrey M. Richter, 1996 (ISBN:1-57231-548-2)
NTDEV—Windows NT device drivers: To subscribe, send "SUBSCRIBE NTDEV" in the body of a message to majordomo@atria.com.
NTIFS—Windows NT installable file systems: To subscribe, send "SUBSCRIBE NTDEV" in the body of a message to majordomo@atria.com.
The VCOMM mailing list—Win32 Comm API and Driver Issues: For more information, send "info VCOMM" in the body of a message to majordomo@corp.nsc.com.
© 1999 Microsoft Corporation