
UDI Developer’s Toolkit
Universal Debugger Interface Specification
6-13
The targets,
dos386/smalldfe.exe
and
dos386/smalltip.exe
src/uditools/makefile.pc
can be used as templates for protected–mode DFE
and TIP development on PC hosts. The support assumes the use of the
MetaWare High C 386 (or Watcom compiler) and Phar Lap DOS extender.
The
isstip.exe
executable (which requires access to large amounts of memory
at runtime to simulate 29K memory) has, in fact, been built using this method.
To build a 386 protected–mode TIP:
Compile your own TIP code with the MetaWare High C 386 compiler.
Similarly compile
dos2udip.c
,
d386cmn.c
, and
realcopy.c
with the
MetaWare High C 386 ompiler, including:
DMSDOS -DDOS386
on the command line.
Assemble
dostip.asm
and
d386cmna.asm
with the Phar Lap 386
assembler with the command line:
386asm -DDOS386 xxx.asm
Link all the above
.objs
using the Phar Lap 386 linker command file shown in
src/uditools/makefile.pc
. You should assume that all the linker directives
shown in that example are important. It is also required that the sections
defined in the
.asm
files,
dostip.asm
, and
d386cmna.asm
, appear in the first
64 K of the final link. This can be done by placing these
.objs
first in the link
order.
To build a 386 protected–mode DFE:
Compile your own DFE code with the MetaWare High C compiler.
Similarly compile
udip2dos.c
,
d386dfe.c
,
d386cmn.c
, and
realcopy.c
with the MetaWare High C compiler, including:
DMSDOS -DDOS386
on the command line.
Assemble
dosdfe.asm
and
d386cmna.asm
with the Phar Lap 386
assembler with the command line:
386asm -DDOS386 xxx.asm