Re: OSkit and Cygwin

• To: "Gregg C Levine" <hansolofalcon@worldnet.att.net>
• Subject: Re: OSkit and Cygwin
• From: Roland McGrath <roland@frob.com>
• Date: Sat, 9 Jun 2001 17:33:43 -0400 (EDT)
• Cc: "Oskit-Users" <oskit-users@fast.cs.utah.edu>
• In-Reply-To: Gregg C Levine's message of Sat, 9 June 2001 17:07:23 -0400 <CMEJIBBFMDBIJJMCINJOAEHDDJAA.hansolofalcon@worldnet.att.net>
• Sender: owner-oskit-users@fast.cs.utah.edu

Leaving aside the "oskit on unix" option (that only works on a few
particular unix systems anyway), the oskit requires nothing in the way of a
"host" environment to build against, and its only tools requirements are
gcc, GNU binutils, GNU make, and the usual ancillary stuff associated with
using autoconf-based configure scripts.  I believe all of that is par for
the course in the cygwin world (about which I have no real clue), i.e. they
provide a bash that works with configure scripts, sed and so forth.

There shouldn't be anything you need to do in the way of porting the oskit
code itself, just details of the configure scripts and makefiles that might 
have some problems with the cygwin environment.

• Re: OSkit and Cygwin
• From: Leigh Stoller <stoller@cs.utah.edu>

• OSkit and Cygwin
• From: "Gregg C Levine" <hansolofalcon@worldnet.att.net>

• Prev: OSkit and Cygwin
• Next: Preferred building environment for OSkit
• Index(es):
  • Main
  • Thread