📄 win_compiling.html.en
字号:
<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --><title>Compiling Apache for Microsoft Windows - Apache HTTP Server</title><link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /><link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /><link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link href="../images/favicon.ico" rel="shortcut icon" /></head><body id="manual-page"><div id="page-header"><p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p><p class="apache">Apache HTTP Server Version 2.0</p><img alt="" src="../images/feather.gif" /></div><div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div><div id="path"><a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.0</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Compiling Apache for Microsoft Windows</h1><div class="toplang"><p><span>Available Languages: </span><a href="../en/platform/win_compiling.html" title="English"> en </a> |<a href="../ko/platform/win_compiling.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p></div> <p>There are many important points before you begin compiling Apache. See <a href="windows.html">Using Apache with Microsoft Windows</a> before you begin.</p> </div><div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#requirements">Requirements</a></li><li><img alt="" src="../images/down.gif" /> <a href="#commandbuild">Command-Line Build</a></li><li><img alt="" src="../images/down.gif" /> <a href="#workspacebuild">Developer Studio Workspace IDE Build</a></li><li><img alt="" src="../images/down.gif" /> <a href="#projectcomponents">Project Components</a></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="requirements" id="requirements">Requirements</a></h2> <p>Compiling Apache requires the following environment to be properly installed:</p> <ul> <li> <p>Disk Space</p> <p>Make sure you have at least 50 MB of free disk space available. After installation Apache requires approximately 10 MB of disk space, plus space for log and cache files, which can grow rapidly. The actual disk space requirements will vary considerably based on your chosen configuration and any third-party modules or libraries.</p> </li> <li> <p>Microsoft Visual C++ 5.0 or higher.</p> <p>Apache can be built using the command line tools, or from within the Visual Studio IDE Workbench. The command line build requires the environment to reflect the <code>PATH</code>, <code>INCLUDE</code>, <code>LIB</code> and other variables that can be configured with the <code>vcvars32</code> batch file:</p> <div class="example"><p><code> "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat" </code></p></div> </li> <li> <p>The Windows Platform SDK.</p> <p>Visual C++ 5.0 builds require an updated Microsoft Windows Platform SDK to enable some Apache features. For command line builds, the Platform SDK environment is prepared by the <code>setenv</code> batch file:</p> <div class="example"><p><code> "c:\Program Files\Platform SDK\setenv.bat" </code></p></div> <p>The Platform SDK files distributed with Visual C++ 6.0 and later are sufficient, so users of later version may skip this requirement.</p> <div class="note">Note that the Windows Platform SDK update is required to enable all supported <code class="module"><a href="../mod/mod_isapi.html">mod_isapi</a></code> features. Without a recent update, Apache will issue warnings under MSVC++ 5.0 that some <code class="module"><a href="../mod/mod_isapi.html">mod_isapi</a></code> features will be disabled. Look for the update at <a href="http://msdn.microsoft.com/downloads/sdks/platform/platform.asp">http://msdn.microsoft.com/downloads/sdks/platform/platform.asp</a>.</div> </li> <li> <p>The awk utility (awk, gawk or similar).</p> <p>To install Apache within the build system, several files are modified using the <code>awk.exe</code> utility. awk was chosen since it is a very small download (compared with Perl or WSH/VB) and accomplishes the task of generating files. Brian Kernighan's <a href="http://cm.bell-labs.com/cm/cs/who/bwk/">http://cm.bell-labs.com/cm/cs/who/bwk/</a> site has a compiled native Win32 binary, <a href="http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe">http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe</a> which you must save with the name <code>awk.exe</code> rather than <code>awk95.exe</code>.</p> <div class="note">Note that Developer Studio IDE will only find <code>awk.exe</code> from the Tools menu Options... Directories tab (the Projects - VC++ Directories pane in Developer Studio 7.0) listing Executable file paths. Add the path for <code>awk.exe</code> to this list, and your system <code>PATH</code> environment variable, as needed.</div> <div class="note">Also note that if you are using Cygwin (<a href="http://www.cygwin.com/">http://www.cygwin.com/</a>) the awk utility is named <code>gawk.exe</code> and that the file <code>awk.exe</code> is really a symlink to the <code>gawk.exe</code> file. The Windows command shell does not recognize symlinks, and because of that building InstallBin will fail. A workaround is to delete <code>awk.exe</code> from the cygwin installation and rename <code>gawk.exe</code> to <code>awk.exe</code>.</div> </li> <li> <p>[Optional] OpenSSL libraries (for <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> and <code>ab.exe</code> with ssl support)</p> <p><strong>Caution: there are significant restrictions and prohibitions on the use and distribution of strong cryptography and patented intellectual property throughout the world.</strong> OpenSSL includes strong cryptography controlled by both export regulations and domestic law, as well as intellectual property protected by patent, in the United States and elsewhere. Neither the Apache Software Foundation nor the OpenSSL project can provide legal advise regarding possession, use, or distribution of the code provided by the OpenSSL project. <strong>Consult your own legal counsel, you are responsible for your own actions.</strong></p> <p>OpenSSL must be installed into a <code>srclib</code> subdirectory named <code>openssl</code>, obtained from <a href="http://www.openssl.org/source/">http://www.openssl.org/source/</a>, in order to compile <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> or the abs project (<code>ab.exe</code> with SSL support.) To prepare OpenSSL for both <code>release</code> and <code>debug</code> builds of Apache, and disable the patent protected features in OpenSSL, you might use the following build commands:</p> <div class="example"><p><code> perl Configure VC-WIN32<br /> perl util\mkfiles.pl >MINFO<br /> perl util\mk1mf.pl dll no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.rel<br /> perl util\mk1mf.pl dll debug no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.dbg<br /> perl util\mkdef.pl 32 libeay no-asm no-mdc2 no-rc5 no-idea >ms\libeay32.def<br /> perl util\mkdef.pl 32 ssleay no-asm no-mdc2 no-rc5 no-idea >ms\ssleay32.def<br /> nmake -f makefile.rel<br /> nmake -f makefile.dbg </code></p></div> <p>Note; you can use the scripts in the <code>ms\</code> subdirectory, however, it's rather tricky to force <code>ms\do_masm.bat</code>, for example, to perform the patent encumberances as mentioned above. Patches to add the $* argument list to the appropriate .bat lines in these scripts aren't incorporated, thus far.</p> </li> <li> <p>[Optional] zlib sources (for <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>)</p> <p>Zlib must be installed into a <code>srclib</code> subdirectory named <code>zlib</code>, however those sources need not be compiled. The build system will compile the compression sources directly into the <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code> module. Zlib can be obtained from <a href="http://www.zlib.net/">http://www.zlib.net/</a> -- <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code> is confirmed to build correctly with version 1.1.4. To use a later version of zlib, upgrade to Apache HTTP Server release 2.2 or later.</p> </li> </ul> </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="commandbuild" id="commandbuild">Command-Line Build</a></h2> <p>First, unpack the Apache distribution into an appropriate directory. Open a command-line prompt and <code>cd</code> to that directory.</p> <p>The master Apache makefile instructions are contained in the <code>Makefile.win</code> file. To compile Apache on Windows NT, simply use one of the following commands to compiled the <code>release</code> or <code>debug</code> build, respectively:</p> <div class="example"><pre>nmake /f Makefile.win _apachernmake /f Makefile.win _apached </pre></div> <p>Either command will compile Apache. The latter will include debugging information in the resulting files, making it easier to find bugs and track down problems.</p> </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="workspacebuild" id="workspacebuild">Developer Studio Workspace IDE Build</a></h2> <p>Apache can also be compiled using VC++'s Visual Studio development environment. To simplify this process, a Visual Studio workspace, <code>Apache.dsw</code>, is provided. This workspace exposes the entire list of working <code>.dsp</code> projects that are required for the complete Apache binary release. It includes dependencies between the projects to assure that they are built in the appropriate order.</p> <p>Open the <code>Apache.dsw</code> workspace, and select <code>InstallBin</code> (<code>Release</code> or <code>Debug</code> build, as desired) as the Active Project. <code>InstallBin</code> causes all related project to be built, and then invokes <code>Makefile.win</code> to move the compiled executables and dlls. You may personalize the <code>INSTDIR=</code> choice by changing <code>InstallBin</code>'s Settings, General tab, Build command line entry. <code>INSTDIR</code> defaults to the <code>/Apache2</code> directory. If you only want a test compile (without installing) you may build the <code>BuildBin</code> project instead.</p> <p>The <code>.dsp</code> project files are distributed in Visual⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -