Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!garnet.berkeley.edu!ked
From: ked@garnet.berkeley.edu (Earl H. Kinmonth)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DOS cross development tools
Keywords: compilers assemblers DOS
Message-ID: <21588@agate.BERKELEY.EDU>
Date: 14 Mar 89 04:48:05 GMT
References: <175@dms3b1.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 23

In article <175@dms3b1.UUCP> dave@dms3b1.UUCP (Dave Hanna) writes:
>Does anyone know of an available cross development package
>that will run on a 68000 UNIX machine and produce DOS object
>and/or .EXE files (preferably Turbo-C/Turbo-Debug compatible)?

I find this request hard to understand. Being able to produce
.exe files under a 68000 system is of questionable utility.  In
one or two passes, you'll probably find bugs under MSDOS and want to
recompile. For that, you'll run Turbo C under MSDOS to get object files
to link.

What you can do is get the MKS Toolkit. This will give you a
pseudo-Unix environment under Miserable DOS. I shift easily between a
Sun and MSDOS using the MKS Toolkit under MSDOS. Of course, I
regenerate object code when I shift. There are a few header files to
make conditional, but Turbo C 2.0 is much better than 1.0 in this
respect.

If you really want to generate Miserable Dos code under **IX, you can
get SCO Xenix.  The cross compiler will generate .obj and .exe files
while running **IX.   You can then move these to Miserable Dos.  I
stopped doing this when I got Turbo C.  The time to regenerate .obj
and .exe files is not that much more than the time to copy them.