Cygwin

From Free net encyclopedia

Cygwin is a collection of free software tools originally developed by Cygnus Solutions to allow various versions of Microsoft Windows to act somewhat like a Unix system. It aims mainly at porting software that runs on POSIX systems (such as Linux systems, BSD systems, and Unix systems) to run on Windows with little more than a recompilation. Programs ported with Cygwin work best on Windows NT, Windows 2000, Windows XP, and Windows Server 2003, but some may run acceptably on Windows 95 and Windows 98. Cygwin is currently maintained by employees of Red Hat and others.

1 Description
2 History
3 See also
4 External links

[edit]

Description

Cygwin consists of a library that implements the POSIX system call API in terms of Win32 system calls, a GNU development toolchain (such as GCC and GDB) to allow basic software development tasks, and some application programs equivalent to common programs on the Unix system. It added the X Window System in 2001.

The package also includes a library called MinGW that works with the native MSVCRT library (Windows API) included with Windows; MinGW has less RAM and disk overhead, operates under a permissive (non-copyleft) license, and can link to any software, but it does not implement as much of the POSIX specification as the Cygwin library does.

Cygwin has no direct support for Unicode, nor does it support any character sets except the current Windows and OEM codepages of your system (e.g., for a Russian user, the only codepages available will be CP1251 and CP866, but not KOI8-R, ISO 8859-5, UTF-8 or anything else). iconv is provided, so it is possible to work with files in other encodings, but conversion must be performed manually.

Red Hat normally licenses the Cygwin library under the GNU General Public License with an exception to allow linking to any free software whose license conforms to the Open Source Definition. (Red Hat also sells commercial licenses to those who wish to redistribute programs that use the Cygwin library under proprietary terms.)

One can subscribe to one of many Cygwin-related mailing lists at the Cygwin Mailing Lists page.

[edit]

History

Cygwin began in 1995 as a project of Steve Chamberlain, a Cygnus engineer who observed that Windows NT and 95 used COFF as their object file format, and that GNU already included support for x86 and COFF, and the C library newlib; so at least in theory it should not be difficult to retarget GCC and get a cross compiler producing executables that would run on Windows. This proved to be so in practice, and a prototype came up quickly.

The next step was to attempt to bootstrap the compiler on a Windows system, but this required enough emulation of Unix to let the GNU configure shell script run, which requires a shell like bash, which in turn requires fork and standard I/O. Windows includes similar functionality, so the Cygwin library proper just needs to translate calls and manage private versions of data, such as file descriptors.

By 1996, other engineers had joined in, since it was clear that Cygwin would be a useful way to provide Cygnus' embedded tools hosted on Windows systems (the previous strategy had been to use DJGPP). It was especially attractive because it was possible to do a three-way cross-compile, for instance to use a hefty Sun workstation to build, say, a Windows-x-MIPS cross-compiler, which was faster than using the PC of the time. Starting around 1998, Cygnus also began offering the Cygwin package as a product of interest in its own right.

[edit]