Date: Fri, 26 Mar 1999 22:43:23 -0500
Message-Id: <199903270343.WAA18483@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <bpmurray*STUFFER*-2603991904090001@macmac-2.ucsf.edu>
Subject: Re: DJGPP: the future is... ?
References: <199903260517 DOT AAA32193 AT envy DOT delorie DOT com> <36FBE6A6 DOT D1407A64 AT cableol DOT co DOT uk> <bpmurray*STUFFER*-2603991904090001 AT macmac-2 DOT ucsf DOT edu>
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> DJGPP for the Mac.

Porting gcc to any platform involves at *least* the following:

* Many machines for developers

* suitable documentation, not only about the CPU but about the OS's
  API, file formats, etc.

* suitable API libraries, or write them from documentation

* money to buy the time required to implement it

If someone can come up with these, you're best bet is to hire Cygnus
to do the port - they have far more concentrated resources that are
geared towards doing that kind of thing.  I suppose if a thousand of
you got together and chipped in a couple hundred bucks each, you'd
have enough to get it done in under a year.  Don't underestimate the
amount of people-hours that went into DJGPP - even with dozens of us
working on it most of the time, it still took *years* to do version 2,
and we'd already done it once!