From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ryan Underwood <nemesis-lists@icequake.net>
Subject: Re: using elks-libc for DOS development
Date: Fri, 5 Mar 2004 15:44:19 -0600
Sender: linux-8086-owner@vger.kernel.org
Message-ID: <20040305214419.GA17957@dbz.icequake.net>
References: <20040305074216.GE3291@dbz.icequake.net> <200403051103.19224.dg@cowlark.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB"
Return-path: <linux-8086-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <200403051103.19224.dg@cowlark.com>
List-Id: <linux-8086.vger.kernel.org>
To: linux-8086@vger.kernel.org


--DocE+STaALJfprDB
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On Fri, Mar 05, 2004 at 11:03:18AM +0000, David Given wrote:
> > would be a waste, as well as the bloat of glibc.  I guess there is
> > Open Watcom now, but does anyone have experience doing small footprint
> > (8086 <=3D 1MB) C development with it?
>=20
> Nope. I gather it works, though.

So did I.  I think I will give it a shot.  I preferred bcc/ELKS-libc
because I could build directly from a Linux host without having to use
WINE/DOSEMU.  But I think Watcom will suffice if the ELKS libc proves to
be too slim.

> However, if you know where to look there are a number of free 16-bit DOS=
=20
> compilers. Leaving aside all the various CP/M86 compilers --- which tend =
to=20
> be K&R only and only compile tiny mode --- a quick web search reveals the=
se:
>=20
> http://www.htsoft.com/products/pacific/
> http://www.digitalmars.com/download/freecompiler.html

Thanks.  I actually ran across these while digging around but didn't pay
much attention.  Both look like fairly complete packages.

> You may be better off sticking with Turbo C, however; it is free, and you=
 seem=20
> to be set up for it.

Well, by "set up for it" I've downloaded a copy and ran it in DOSEMU. I
also have some experience with it, having used it years ago.  But, I
don't know if it is right for an embedded project.  Are there any
licensing issues to worry about or any rot like that?  I liked the idea
of using FreeDOS/RxDOS and the ELKS C library because there were no
restrictions on any of them besides the *GPL ones of needing to make the
source code available to end users.  I'm not sure what using a
proprietary C library would get me into.  I think with the two compilers
you mentioned, I should be safe though.

thanks!

--=20
Ryan Underwood, <nemesis@icequake.net>

--DocE+STaALJfprDB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFASPSzIonHnh+67jkRAq0vAKCkjD9UVpU4evJRVSKF2pK6buuaswCfRcdk
y2A4fhUGyXTBEg7ICOyzm9s=
=/xUQ
-----END PGP SIGNATURE-----

--DocE+STaALJfprDB--