On Thu, Apr 06, 2000 at 09:17:12PM -0400, Bill Pechter
wrote:
I've got an unused IBM OS/2 C compiler...
also there's always GCC...
What do you need...
The problem isn't so much generating code, as linking it into .DLL files.
I burned off a *lot* of brain cells writing a linking loader for Win16 "NE"
format .DLL files (ooh I hate Microsoft *SO MUCH*), and I'm really not excited
about the idea of starting from scratch and writing an ELF loader too, just
to use GCC output. Although in the long run that may be necessary. Anyway,
all of the good ol' LINK/TLINK/WLINK linkers from Win16 days will generate
these files OK, but normally they'll *also* link in a startup module which
makes a bunch of Win16 calls before calling the user's LibMain() routine.
Faking those Win16 entry points is a pain, but figuring out the undocumented
guts of the respective C libraries and writing a replacement startup module
for each one, just for running under E11, would be even more of a pain.
Geez... I thought the gcc for dos could do what you need...
and have been
hoping for the
KL equivalent someday...
One of these days!
John Wilson
D Bit
Bill
--
bpechter(a)monmouth.com | Microsoft: Where do you want to go today?
| Linux: Where do you want to go tomorrow?
| BSD: Are you guys coming, or what?