Hi, attached is an update manual html page specific for the Cygwin platform. Please review and add this to the current cvs tree.
Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you areTitle: Using Apache with Cygwin
Apache HTTP ServerUsing Apache with CygwinThis document explains how to install, configure and run Apache 1.3 under the Cygwin layer for Microsoft Windows. Cygwin is a POSIX.1 emulation layer for 32-bit Microsoft Windows operating systems. The Apache Group does not guarantee that this software will work as documented, or even at all. If you find any bugs, please document them on our bug reporting page. Latest development news, pre-compiled distribution binaries, and third-party modules as DLLs, may be found at http://apache.dev.wapme.net/. Contributions are highly welcome (please see TODO list); please submit your code or suggestions to the bug report page, or join the [EMAIL PROTECTED] mailing list. The Win32 port of Apache is built on its own, custom code within Apache to assure interoperability with Windows operating systems. While it is considered release quality, it is slower and less thoroughly tested than the Unix ports. The Cygwin alternative uses the well tested Unix code by using the Cygwin portability layer for POSIX.1 emulation. The Cygwin port may suffer from gaps in security or reliability due to the interaction of the Cygwin compatibility layer with the native Windows API. The Win32 port will be more familiar to most Windows users. The Cygwin port (including the build environment) will be more familiar to Unix admins and developers. Due to these two different code bases, the security and reliability of the two ports are unrelated to each other. The Win32 port should be considered the more secure of the two at this time. The Win32 port is recommended for most Windows users, however the Cygwin port offers an extra layer of compatibility for Unix developers. Apache still performs best, and is most reliable, on Unix platforms. First benchmarks have shown that the same Apache setup on Cygwin performs about 30% slower than the corresponding native Windows version. Most of this document assumes that you have a working Cygwin installation and want to compile Apache yourself from the original distribution sources.
History of Apache for CygwinCygwin support for Apache began with Apache 1.2.6 and Cygwin b18. Due to licensing issues there has not been an official binary distribution until Red Hat Inc. (who merged with Cygnus Solutions Inc.) changed their Cygwin license to ensure compiled executables do not fall under GPL license if the distributed software is considered as open source. Cygwin is supported in the official source distributions
from Apache 1.3.20 and later. Pre-compiled binaries for the
Cygwin platform (without the Differences from Apache for Windows (native)Both versions, Apache for Windows and Apache for Cygwin, are designed to run on the same operating systems, the Windows NT and Windows 2000 family. But there are considerable differences between the two flavors. While Apache for Windows is a native Windows port, Apache
for Cygwin relies on the Cygwin POSIX.1 emulation layer
provided by the Most significant differences are the amount of changes to the source code needed to compile and run Apache on the Cygwin platform. While the native Windows port needs major changes and platform specific additions, the Cygwin based port changes are very small and most of the Unix source code can be used without major changes on the Cygwin platform. When to use Apache for Cygwin and/or Apache versus
Windows? If you are using Windows NT or Windows 2000 for development
and office purposes, but your productive HTTP server
environments are Unix based systems, you may use Apache for
Cygwin to develop on Windows and simply copy whole Apache
configurations (i.e., What about modules ( While there are developers who directly support the Windows native port of Apache, very few module developers do. That is why it is can be difficult to make a Unix-based Apache installation with third-party modules work the same way on the Windows side using the native port. Apache for Cygwin makes this much easier. What are the differences in the configuration
files? # httpd.conf (for Windows) DocumentRoot "c:/apache/htdocs"Apache for Cygwin can use unmodified POSIX style path names like # httpd.conf (for Cygwin) DocumentRoot "/usr/local/apache/htdocs" What about performance? This is to be expected, because Cygwin emulates a Unix environment on a "foreign" operating system, while Apache for Windows uses Windows code in its own native environment. First benchmark results have shown that Apache for Cygwin is about 30% slower than native Apache for Windows counterpart. RequirementsThis Apache 1.3 port for Cygwin is designed to run on Windows NT 4.0 and Windows 2000, NOT on Windows 95 or 98. Windows NT 4.0 and Windows 2000 have both been successfully tested and approved. In all cases TCP/IP networking must be installed. Cygwin 1.x is required to compile and run this version. Cygwin 1.3.9 and 1.3.10 have been tested and approved on both supported OSes. We suggest to use Cygwin 1.3.9-2 and higher. Note:If you want to compile shared DLL
modules using Downloading Apache for CygwinThe Cygwin platform is supported out of the box by Apache 1.3.20 and later. This means there is no extra download required for the Cygwin platform. The latest version of Apache can be found on the Apache httpd web site at http://httpd.apache.org/. The site lists the current release, any more recent development versions, and information on any mirror sites. What about Cygwin Net Distribution binaries? Configuring and Installing Apache for CygwinApache on Cygwin is configured and compiled the same way as on most Unix systems. Refer to the general configuration and installation documents for details. There are three ways to configure and build Apache for Cygwin, depending on how additional Apache modules should be used:
Using Win32 native socket implementation insteadApache for Cygwin support an option to use the Win32 native
socket calls instead of Cygwin's POSIX wrappers internally. To
use the Win32 native socket calls configure Apache for Cygwin
with the $ cd apache_1.3.x $ ./configure --enable-rule=CYGWIN_WINSOCK [...] $ make Using Win32 native socket calls is intended for performance reasons and as a hybrid way to interact with the underlying native socket implementation. Running Apache for CygwinApache on Cygwin can be started and stopped in the same
manner as on Unix systems. You may also use the
Running Apache for Cygwin as a ServiceApache on Cygwin can be invoked as a Windows NT or Windows
2000 service. Cygwin has its own
Please refer to the Any additional contributions to this document and the Cygwin support for Apache are highly welcome. Please send them to Stipe Tolj <[EMAIL PROTECTED]>. Apache HTTP Server |