Date: Thu, 22 Jan 1998 18:42:23 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Jason A Bennett <jasonb AT gfsmortgage DOT com>
cc: "'djgpp AT delorie DOT com'" <djgpp AT delorie DOT com>
Subject: Re: Port from DOS/16M
In-Reply-To: <01BD2683.A52CA660@ŻJASONB>
Message-ID: <Pine.SUN.3.91.980122184204.1427H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 21 Jan 1998, Jason A Bennett wrote:

> So, in lieu of the online guide being finished (would love that porting 
> section)

So would we.  In the meantime, you can look into the DJGPP FAQ list
(v2/faq210b.zip from the same place you get DJGPP), for some advice.

> what generally will be involved in porting from 16M to DJGPP? 
> Will it just be a quick library recompile and change a few calls, or more?

It depends on what that program does.  If it doesn't use any
DOS-specific stuff, like accessing the video adapter or other
memory-mapped devices, or using DOS/BIOS services via the `int86'
functions or its brethren, then you shouldn't need much more than a
simple recompile.

The DOS-specific stuff like what's mentioned above needs more work,
because DJGPP does it differently due to the protected-mode
environment in which it runs your code.

In sum, if the original code is ANSI or POSIX, it will need only minor
rework.  Telling more about the program might yield more accurate
assessment of the porting effort.