Building the drivers
The first thing you need to do is install OpenWatcom 1.7a or higher. You need to install at least the 16-bit and 32-bit OS/2 targets. It is assumed that you will be installing the OS/2 hosted version of Open Watcom.
Install the DDK
If you are going to build uniaud16, you need to install the IBM Driver Development Kit (DDK) Toolkit. IBM no longer makes this toolkit publicly available. The long term plan is to implement open source versions of the DDK headers in OpenWatcom and this will eliminate the need for the DDK to build Uniaud.
Install ilink or lxlite
Either ilink or wlink can be used, but when using wlink, lxlite is required to shrink the binary to a reasonable size.
Install ACPI Toolkit
If building with ACPI support, the ACPI developer toolkit is required.
Configure the build environment
Now you need to build Makefile.inc. This file configures the uniaud makefiles for your specific directory layout. Assuming directory layout described in Getting the sources, run
cd uniaud32_workspace\trunk configure
and answer the questions.
To build uniaud32, do whatever you do that make the OpenWatcom available in the current command line session and then
!m_kee.cmd is a simple wmake front-end.
The 3 build types are:
- ACPI: The default.
- KEE: If for some reason you do not want to build with ACPI. Set ACPI=0
- W4: For support for older kernels, such as that in Warp 3. Mostly untested at this point. Set KEE=0
A full build should take less than 15? minutes on reasonably capable hardware and should complete without errors or warnings.
It is considered bad practice to commit sources that do not build error and warning free to the subversion repository. However, when multiple developers are making concurrent changes, this can happen.
To build uniaud16
cd uniaud16_workspace\trunk wmake drv
A full build should take less than 5? minutes on reasonably capable hardware and should complete without errors or warnings