Xref: news-dnh.mv.net comp.os.msdos.djgpp:963
Path: news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!news.mathworks.com!uunet!in1.uu.net!noc.near.net!das-news2.harvard.edu!oitnews.harvard.edu!news.sesqui.net!rice!news!sandmann
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Stand-alone djgpp-compiled programs.
Date: Tue, 18 Jul 1995 12:53:45 CDT
Organization: Rice University, Houston, Texas
Lines: 13
References: <3ugnvu$h68 AT newsbf02 DOT news DOT aol DOT com>
Reply-To: sandmann AT clio DOT rice DOT edu
Nntp-Posting-Host: clio.rice.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

> Is it possible to write stand-alone djgpp programs (you know, so I can run
> the program on a machine that doesn't have go32 on it)? If so.. how's it done?

Under V1.x, you coff2exe -s go32.exe yourprog.out, and the image should
be standalone unless it needs coprocessor instructions (and you can put
emu387 in the same directory and solve that problem for '87 less boxes).

Under V2.0, each image is standalone automatically if DPMI is available.
Since that can't be guaranteed, you can copy cwsdpmi.exe into the same
directory which will be loaded and provide DPMI services.  Under V2 you
can link the 387 emulator into the code by specifying -lemu; or you
can copy emu387.dxe into the same directory and it will be found and
dynamically loaded if needed.