When you are comfortable with the changes you have made to the OEMDONGL.C source code, it is time to build your version of OEMDONGL.VXD. A MAKEFILE in the DDK subdirectory contains all the directives the compiler, assembler, and linker need to create OEMDONGL.VXD. Before you run the MAKEFILE, you have to match it to your the build environment by carrying out the steps below.
First, check the lines in the MAKEFILE that define the build environment to make sure the variable settings match your build environment. The lines of the MAKEFILE you must check are right at the beginning of the MAKEFILE and are shown below:
#Change the following variables for your environment #################################################### CC=..\..\..\..\dev\tools\c932\bin\cl.exe LINK=..\..\..\..\dev\tools\c932\bin\link.exe MASM=..\..\..\..\dev\tools\masm611c\mlx DDKLIB=..\..\..\..\dev\ddk\lib DDKINCLUDE=..\..\..\..\dev\ddk\inc H2INC=..\..\..\..\dev\tools\common\h2inc.exe MAPSYM=..\..\..\..\..\dev\tools\common\mapsym
You may have to edit one or more of these seven lines in order to match the paths in your build environment.
You may also want to edit the MAKEFILE in order to name your VxD something other than OEMDONGL.VXD. Using the REDEYE-88 project as an example again, you would replace all the instances of the case-insensitive string "OEMDONGL" in the MAKEFILE with "RED88" if you wanted the VxD executable file to be named RED88.VXD.
If you edit the MAKEFILE to name the VxD the MAKEFILE produces to something other than OEMDONGL.VXD, then you must also edit the VxD wrapper source code in CVXDCTRL.ASM to reflect that name change. Using the REDEYE-88 example again, you would replace all instances of the case-insensitive string "OEMDONGL" in CVXDCTRL.ASM with "RED88."
When you are sure the MAKEFILE matches your build environment and the VxD will have the name you want, you can build your VxD. To build a retail version of your VxD, change the current directory to the DDK subdirectory and then enter the command
nmake retail
To build a debug version of your VxD, change the current directory to the DDK subdirectory and then enter the command
nmake debug
You can also build a debug version by simply using the command
nmake
To build both a retail and debug version, use the command
nmake all
Creating an installation diskette that includes your VxD is described in Creating an Installation Diskette and Installing the IR Communications Software.
After you complete this step, you can use the installation diskette to install IR Communications for Windows 95 on one or more Windows 95 computers and try it out.