From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-8086@vger.kernel.org
Subject: using elks-libc for DOS development
Date: Fri, 5 Mar 2004 01:42:16 -0600 [thread overview]
Message-ID: <20040305074216.GE3291@dbz.icequake.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
Hi,
I want to do some 16-bit development for FreeDOS on embedded 8086.
Is bcc + ELKS libc suitable enough to e.g. replace Turbo C for this
task? Looking through the source, I see some normal functions like
geninterrupt() are stubbed out, and some other things like intdos do not
exist. Basically, I need to use software interrupts for DOS API, and to
install my own interrupt handler as a TSR and invoke it from another
program too. I am also needing to handle external hardware interrupts
such as the system timer.
Besides ELKS libc, are there any other free C libraries suitable for
16-bit DOS application development? I find a 16-bit version of DJGPP,
but it has no C library. :( I would use a 32-bit version of DJGPP, but
the device only has 512k of memory; the necessity of the DPMI server
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 <= 1MB) C development with it?
Thanks!
--
Ryan Underwood, <nemesis@icequake.net>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-03-05 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 7:42 Ryan Underwood [this message]
2004-03-05 11:03 ` using elks-libc for DOS development David Given
2004-03-05 21:44 ` Ryan Underwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040305074216.GE3291@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox