| | 10 | Next 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 Toolkit headers in OpenWatcom which will eliminate the need for the DDK. |
| | 11 | |
| | 12 | Now you need to build Makefile.inc. This file configures the uniaud makefiles for your specific directory layout. Assuming directory layout described in [WikeStart#Gettingthesources Getting the sources], run |
| | 13 | |
| | 14 | {{{ |
| | 15 | cd uniaud32_workspace |
| | 16 | trunk\configure |
| | 17 | }}} |
| | 18 | |
| | 19 | and answer the questions. Review the generated Makefile.inc and verify that the pathnames are correct. This script has some issues. |
| | 20 | |
| | 21 | Once you are satisfied, copy the file to the root of your uniaud16 workspace. This is the uniaud16_workspace referred to in the examples [WikeStart#Gettingthesources Getting the Sources]. There really should need to be only one instance of this file, but this will have to wait until the makefiles get some rework. |
| | 22 | |
| | 23 | To build uniaud32, do whatever you do that make the OpenWatcom available in the current command line session and then |
| | 24 | |
| | 25 | {{{ |
| | 26 | cd uniaud32_workspace\trunk |
| | 27 | !m_kee.cmd |
| | 28 | }}} |
| | 29 | |
| | 30 | !m_kee.cmd is a simple wmake front-end. |
| | 31 | |
| | 32 | A full build should take about 15? minutes on reasonably capable hardware. |
| | 33 | |
| | 34 | To build uniaud16, do |
| | 35 | |
| | 36 | {{{ |
| | 37 | cd uniaud16_workspace\trunk |
| | 38 | wmake -ms -f makefile.os2 |
| | 39 | }}} |
| | 40 | |
| | 41 | A full build should take less than 5? minutes on reasonably capable hardware. |