Building the drivers =

The original build instructions are at ​http://svn.netlabs.org/repos/uniaud/GPL/trunk/howtobuild.txt

The new build instructions are here.

The first thing you need to do is install ​OpenWatcom. You need to install at least the OS/2 C and C++ support for OS/2 16-bit and 32-bit targets.

If you are going to build uniaud16, you need to install the IBM Driver Development Kit (DDK) Toolkit. IBM no longer makes this toolkit publically available, so if you need a copy TBD. 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.

If you are only building uniaud32, you do not need the DDK.

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. If you don't have a copy of the DDK, enter a syntatically valid path.

Review the generated Makefile.inc and verify that the pathnames are correct. This script has some issues.

Once you are satisfied, copy Makefile.inc to the root of your uniaud16 workspace. This is the uniaud16_workspace referred to in the example Getting the Sources. There really should need to be only one instance of Makefile.inc file, but this will have to wait until the makefiles get some needed rework.

To build uniaud32, do whatever you do that make the OpenWatcom available in the current command line session and then

cd uniaud32_workspace\trunk
!m_kee.cmd

!m_kee.cmd is a simple wmake front-end.

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 -ms -f makefile.os2

A full build should take less than 5? minutes on reasonably capable hardware and should complete without errors or warnings