Date: Sun, 12 Mar 2000 09:05:02 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Mariano Alvarez =?iso-8859-1?Q?Fern=E1ndez?= <malfer AT teleline DOT es>
cc: paul-ml AT is DOT lg DOT ua, djgpp <djgpp AT delorie DOT com>
Subject: Re: [ANN] Announcing PW32 - the DJGPP 'port' to Win32
In-Reply-To: <38C98C44.A475EAE@teleline.es>
Message-ID: <Pine.SUN.3.91.1000312090439.10062B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 11 Mar 2000, Mariano Alvarez =?iso-8859-1?Q?Fern=E1ndez?= wrote:

> >Since I was already somewhat experienced, I took some
> >thought of what to start from, and after very little hesiation,
> >I took the best libc out there one from DJGPP.
> 
> Do you seem possible merge your work with the DJGPP libc to have a dual
> platform library?

This will take much more than just a library.  You need to change the
stub loader and the startup code, so that programs can function as
both DJGPP and Windows PE executable, and you need to change the
low-level functions in the DJGPP libc.a to issue OS calls either to
the Windows native API or to the DPMI API, depending on the mode in
which the executable runs.