Cygwin

From Wikipedia, the free encyclopedia

Cygwin
Running Cygwin under Windows XP
Developed by	Cygnus Solutions, Red Hat and others
Initial release	1995, 12–13 years ago
Latest release	1.5.25-11 / 9 March 2008
Written in	C/C++
OS	Microsoft Windows
Genre	Emulator
License	GNU General Public License
Website	http://www.cygwin.com/

Cygwin (pronounced /ˈsɪɡwɪn/^[1]) is a collection of tools originally developed by Cygnus Solutions to allow versions of Microsoft Windows to behave in ways familiar to Unix users. Programs supported by Cygwin work well on Windows NT, Windows 2000, Windows XP, Windows Vista and some run acceptably on Windows 9x. While Cygwin provides header files and libraries that make it possible to recompile or to port Unix applications for use on computers running Microsoft Windows operating systems, it does not make binaries compatible with such computers running without Cygwin.

Cygwin is currently maintained by employees of Red Hat, NetApp and others. Christopher Faylor is currently the manager of the Cygwin development team. Released under the GNU General Public License, Cygwin is free software.

1 Description
2 History
3 Features
4 Derivatives
5 Additions to Cygwin
6 Alternatives to Cygwin
7 See also
8 References
9 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 a large number of application programs equivalent to those on the Unix system. Many Unix programs have been ported to Cygwin, including the X Window System, KDE, GNOME^[2], Apache, and TeX. Cygwin permits installing inetd, syslogd, sshd, Apache, and other daemons as standard Windows services, allowing Microsoft Windows systems to work like Unix and Linux servers.

All of these programs are installed by running Cygwin's "setup" program, which downloads the necessary files from the Internet. Setup can install, update, and remove programs and download the source code for them.

Efforts to reconcile concepts that differ between Unix and Windows systems include:

A Cygwin-specific version of the Unix mount command allows Windows paths to be mounted as "filesystems" in the Unix file space. Mount information is normally stored in the registry. Filesystems can be mounted as binary ones (by default), or as text-based ones, which enables automatic conversion between LF and CRLF endings. (This only affects programs that call open() or fopen() without specifying text or binary. Programs installed by Cygwin's setup program always open files in binary mode when appropriate, thus avoiding the problem.) Disk drives (C:, D:, etc.) are also denominated /cygdrive/c, /cygdrive/d, etc. Windows network paths of the form \\HOST\SHARE\FILE are mapped to //HOST/SHARE/FILE.
Full-featured /dev and /proc file systems are provided. /proc/registry provides direct filesystem access to the registry.
Symbolic links are provided, and use .LNK files (Windows shortcuts) containing Cygwin-specific information, and with the "system" attribute set to speed up processing. However, native NTFS symbolic links are handled differently; using the rm deletes the linked file instead of the link itself. Old Cygwin versions handled symbolic links using plain text files with hidden attribute set and a single line of text, pointing to the destination file or directory.
The Solaris API for handling access control lists (ACLs) is supported and maps to the Windows NT ACL system.
Special formats of /etc/passwd and /etc/group are provided that include pointers to the Windows equivalent SID's (in the GECOS field), allowing for mapping between Unix and Windows users and groups.
Various utilities are provided for converting between Windows and Unix file formats, for handling line ending (CRLF/LF) issues, for displaying the DLLs that an executable is linked with, etc.
The Cygwin library also interfaces to existing Windows libraries. It is possible to call Windows functions like waveOut from Cygwin executable itself.

The version of gcc that comes with Cygwin has various extensions for creating Windows DLLs, specifying whether a program is a windowing or console mode program, adding resources, etc. It also provides support for compiling MinGW-compatible executables (that is, executables that do not require Cygwin to be installed to run, or more specifically, executables that don't require Cygwin's CYGWIN1.DLL, which provides the POSIX compatibility layer).

Cygwin is used heavily for porting many popular pieces of software to the Windows platform. It is used to compile Mozilla Firefox, Sun Java, OpenOffice.org, and even server software, like lighttpd.

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.)

[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 just needs to properly translate calls and manage private versions of data, such as file descriptors.

Initially Cygwin was called gnuwin32 (not to be confused with the current GnuWin32 project). The name was changed to Cygwin32 to emphasize Cygnus' role in creating it. When Microsoft registered the trademark Win32, the 32 was dropped to simply become Cygwin.

By 1996, other engineers had joined in, because 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] Features

Supports native application building using mingw
Supports remote logins using rsh, ssh, and telnet
Embedded cross platforms support, used for many platforms including PSP and PS2
X Window and OpenGL support
Windows Vista support

[edit] Derivatives

Cygnix is a limited X11 environment based on Cygwin. Its name is an abbreviation of "CYGnus pseudo-uNIX".

There are implementations of Cygnix in Windows 95 / 98 / ME, Windows NT / 2000 / XP, and AmigaOS 4.0.

[edit] Additions to Cygwin

Extensions to Cygwin are available, such as Cygwin/X, a port of the X Window System, and in turn, the KDE Desktop as KDE on Cygwin. However KDE on Cygwin has been phased out as KDE 4 is being ported natively on Windows.

[edit] Alternatives to Cygwin

Several open-source and proprietary alternatives are available for people who need simultaneous access to both MS Windows and UNIX environments on the same hardware.

[edit] Other UNIX emulators for Windows

Toolsets like Microsoft Windows Services for UNIX, MKS Toolkit, UnxUtils, GnuWin32 and UWIN aim to provide a complete POSIX like environment, as does Cygwin. They implement at least a shell, several utilities, including the familiar UNIX compiler tools, including make and the cc commandline interface to the C programming environment. UnxUtils only provides a subset, as it restricts itself to use only the features provided by the Microsoft C Runtime environment.

[edit] Programming tools

MinGW on the contrary, only provides the set of GNU Programming tools, without the interactive environment, with which to port UNIX applications to Windows.

It is also possible to develop applications based on a cross-platform toolkit like Qt, PWLib, allowing those applications to be compiled on either platform and provide users with the same experience.

[edit] Reverse approach

A radically different approach is available with Wine (software), which is a re-implementation of the Windows API and toolset for Linux and similar systems, while virtualisation engines like VMware and Xen allow Windows and Linux or UNIX to run concurrently on top of a hypervisor microkernel. Finally, Cooperative Linux was created to run just Windows and Linux simultaneously on the same hardware.