github.com/krum110487/go-htaccess@v0.0.0-20240316004156-60641c8e7598/tests/data/apache_2_2_34/manual/platform/win_compiling.html.en (about)

     1  <?xml version="1.0" encoding="ISO-8859-1"?>
     2  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
     3  <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
     4  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
     5  <!--
     6          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
     7                This file is generated from xml source: DO NOT EDIT
     8          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
     9        -->
    10  <title>Compiling Apache for Microsoft Windows - Apache HTTP Server Version 2.2</title>
    11  <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
    12  <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
    13  <link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
    14  <script src="../style/scripts/prettify.min.js" type="text/javascript">
    15  </script>
    16  
    17  <link href="../images/favicon.ico" rel="shortcut icon" /><link href="http://httpd.apache.org/docs/current/platform/win_compiling.html" rel="canonical" /></head>
    18  <body id="manual-page"><div id="page-header">
    19  <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
    20  <p class="apache">Apache HTTP Server Version 2.2</p>
    21  <img alt="" src="../images/feather.gif" /></div>
    22  <div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
    23  <div id="path">
    24  <a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Server</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.2</a> &gt; <a href="./">Platform Specific Notes</a></div><div id="page-content"><div class="retired"><h4>Please note</h4>
    25              <p> This document refers to a legacy release (<strong>2.2</strong>) of Apache httpd. The active release (<strong>2.4</strong>) is documented <a href="http://httpd.apache.org/docs/current">here</a>. If you have not already upgraded, please follow <a href="http://httpd.apache.org/docs/current/upgrading.html">this link</a> for more information.</p>
    26          <p>You may follow <a href="http://httpd.apache.org/docs/current/platform/win_compiling.html">this link</a> to go to the current version of this document.</p></div><div id="preamble"><h1>Compiling Apache for Microsoft Windows</h1>
    27  <div class="toplang">
    28  <p><span>Available Languages: </span><a href="../en/platform/win_compiling.html" title="English">&nbsp;en&nbsp;</a> |
    29  <a href="../ko/platform/win_compiling.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a></p>
    30  </div>
    31  
    32  
    33      <p>There are many important points before you begin compiling
    34      Apache. See <a href="windows.html">Using Apache with Microsoft
    35      Windows</a> before you begin.</p>
    36  
    37    </div>
    38  <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#requirements">Requirements</a></li>
    39  <li><img alt="" src="../images/down.gif" /> <a href="#commandbuild">Command-Line Build</a></li>
    40  <li><img alt="" src="../images/down.gif" /> <a href="#workspacebuild">Developer Studio Workspace IDE Build</a></li>
    41  <li><img alt="" src="../images/down.gif" /> <a href="#exportingmakfiles">Exporting command-line .mak files</a></li>
    42  <li><img alt="" src="../images/down.gif" /> <a href="#installation">Installation</a></li>
    43  <li><img alt="" src="../images/down.gif" /> <a href="#projectcomponents-warn">Warning about building Apache from the development tree</a></li>
    44  </ul><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
    45  <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
    46  <div class="section">
    47  <h2><a name="requirements" id="requirements">Requirements</a></h2>
    48  
    49      
    50  
    51      <p>Compiling Apache requires the following environment to be
    52      properly installed:</p>
    53  
    54      <ul>
    55        <li>
    56          <p>Disk Space</p>
    57  
    58          <p>Make sure you have at least 200 MB of free disk space
    59          available. After installation Apache requires approximately
    60          80 MB of disk space, plus space for log and cache files,
    61          which can grow rapidly. The actual disk space requirements
    62          will vary considerably based on your chosen configuration and
    63          any third-party modules or libraries, especially when OpenSSL
    64          is also built.  Because many files are text and very easily
    65          compressed, NTFS filesystem compression cuts these requirements
    66          in half.</p>
    67        </li>
    68  
    69        <li>
    70          <p>Appropriate Patches</p>
    71  
    72          <p>The httpd binary is built with the help of several patches to
    73          third party packages, which ensure the released code is buildable
    74          and debuggable.  These patches are available and distributed from <a href="http://www.apache.org/dist/httpd/binaries/win32/patches_applied/">http://www.apache.org/dist/httpd/binaries/win32/patches_applied/</a>
    75          and are recommended to be applied to obtain identical results as the
    76          "official" ASF distributed binaries.</p>
    77        </li>
    78  
    79        <li>
    80          <p>Microsoft Visual C++ 6.0 (Visual Studio 97) or later.</p>
    81  
    82          <p>Apache can be built using the command line tools, or from
    83          within the Visual Studio IDE Workbench.  The command line
    84          build requires the environment to reflect the <code>PATH</code>,
    85          <code>INCLUDE</code>, <code>LIB</code> and other variables
    86          that can be configured with the <code>vcvars32.bat</code> script.</p>
    87  
    88          <div class="note">You may want the Visual Studio Processor Pack for your older
    89          version of Visual Studio, or a full (not Express) version of newer
    90          Visual Studio editions, for the ml.exe assembler.  This will allow
    91          you to build OpenSSL, if desired, using the more efficient assembly
    92          code implementation.</div>
    93  
    94          <div class="note">Only the Microsoft compiler tool chain is actively supported by
    95          the active httpd contributors.  Although the project regularly accepts
    96          patches to ensure MinGW and other alternative builds work and improve
    97          upon them, they are not actively maintained and are often broken in
    98          the course of normal development.</div>
    99        </li>
   100  
   101        <li>
   102          <p>Updated Microsoft Windows Platform SDK, February 2003 or later.</p>
   103  
   104          <p>An appropriate Windows Platform SDK is included by default in the
   105          full (not express/lite) versions  of Visual C++ 7.1 (Visual Studio 2002)
   106          and later, these users can ignore these steps unless explicitly choosing
   107          a newer or different version of the Platform SDK.</p>
   108  
   109          <p>To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK
   110          environment must be prepared using the <code>setenv.bat</code> 
   111          script (installed by the Platform SDK) before starting the command
   112          line build or launching the msdev/devenv GUI environment.  Installing
   113          the Platform SDK for Visual Studio Express versions (2003 and later)
   114          should adjust the default environment appropriately.</p>
   115  
   116          <div class="example"><p><code>
   117            "c:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32"<br />
   118            "c:\Program Files\Platform SDK\setenv.bat"
   119          </code></p></div>
   120        </li>
   121  
   122        <li>
   123          <p>Perl and awk</p>
   124  
   125          <p>Several steps recommended here require a perl interpreter during
   126          the build preparation process, but it is otherwise not required.</p>
   127   
   128          <p>To install Apache within the build system, several files are
   129          modified using the <code>awk.exe</code> utility. awk was chosen since
   130          it is a very small download (compared with Perl or WSH/VB) and
   131          accomplishes the task of modifying configuration files upon
   132          installation.  Brian Kernighan's
   133          <a href="http://www.cs.princeton.edu/~bwk/btl.mirror/">http://www.cs.princeton.edu/~bwk/btl.mirror/</a>
   134          site has a compiled native Win32 binary,
   135          <a href="http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe">http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe</a> which
   136          you must save with the name <code>awk.exe</code> (rather than
   137          <code>awk95.exe</code>).</p>
   138  
   139          <div class="note">If awk.exe is not found, Makefile.win's install target
   140          will not perform substitutions in the installed .conf files.
   141          You must manually modify the installed .conf files to allow
   142          the server to start.  Search and replace all "@token@" tags
   143          as appropriate.</div>
   144  
   145          <div class="note">The Visual Studio IDE will only find <code>awk.exe</code>
   146          from the PATH, or executable path specified in the menu option
   147          Tools -&gt; Options -&gt; (Projects -&gt;) Directories.  Ensure
   148          awk.exe is in your system path.</div>
   149  
   150          <div class="note">Also note that if you are using Cygwin tools
   151          (<a href="http://www.cygwin.com/">http://www.cygwin.com/</a>) 
   152          the awk utility is named <code>gawk.exe</code> and that the file 
   153          <code>awk.exe</code> is really a symlink to the <code>gawk.exe</code>
   154          file. The Windows command shell does not recognize symlinks, and 
   155          because of this building InstallBin will fail. A workaround is 
   156          to delete <code>awk.exe</code> from the cygwin installation and 
   157          copy <code>gawk.exe</code> to <code>awk.exe</code>.  Also note the
   158          cygwin/mingw ports of gawk 3.0.x were buggy, please upgrade to 3.1.x
   159          before attempting to use any gawk port.</div>
   160        </li>
   161  
   162        <li>
   163          <p>[Optional] zlib library (for <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>)</p>
   164  
   165          <p>Zlib must be installed into a <code>srclib</code> subdirectory named
   166          <code>zlib</code>.  This must be built in-place.  Zlib can be obtained 
   167          from <a href="http://www.zlib.net/">http://www.zlib.net/</a> -- the
   168          <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code> is confirmed to work correctly with 
   169          version 1.2.3.</p>
   170  
   171          <div class="example"><p><code>
   172            nmake -f win32\Makefile.msc<br />
   173            nmake -f win32\Makefile.msc test
   174          </code></p></div>
   175        </li>
   176  
   177        <li>
   178          <p>[Optional] OpenSSL libraries (for <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>
   179          and <code>ab.exe</code> with ssl support)</p>
   180  
   181          <div class="note">The OpenSSL library is cryptographic software.  The country
   182          in which you currently reside may have restrictions on the import,
   183          possession, use, and/or re-export to another country, of encryption
   184          software.  BEFORE using any encryption software, please check your
   185          country's laws, regulations and policies concerning the import,
   186          possession, or use, and re-export of encryption software, to see
   187          if this is permitted.  See 
   188          <a href="http://www.wassenaar.org/">http://www.wassenaar.org/</a>
   189          for more information.</div>
   190  
   191          <p>Configuring and building OpenSSL requires perl to be installed.</p>
   192  
   193          <p>OpenSSL must be installed into a <code>srclib</code> subdirectory 
   194          named <code>openssl</code>, obtained from 
   195          <a href="http://www.openssl.org/source/">http://www.openssl.org/source/</a>, in order to compile 
   196          <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> or the <code>abs.exe</code> project, which
   197          is ab.c with SSL support enabled.  To prepare OpenSSL to be linked 
   198          to Apache mod_ssl or abs.exe, and disable patent encumbered features
   199          in OpenSSL,  you might use the following build commands:</p>
   200  
   201          <div class="example"><p><code>
   202            perl Configure no-rc5 no-idea enable-mdc2 enable-zlib VC-WIN32 
   203                 -Ipath/to/srclib/zlib -Lpath/to/srclib/zlib<br />
   204            ms\do_masm.bat<br />
   205            nmake -f ms\ntdll.mak
   206          </code></p></div>
   207  
   208          <div class="note">It is not advisable to use zlib-dynamic, as that transfers
   209          the cost of deflating SSL streams to the first request which must
   210          load the zlib dll.  Note the suggested patch enables the -L flag to
   211          work with windows builds, corrects the name of zdll.lib and ensures
   212          .pdb files are generated for troubleshooting.  If the assembler is
   213          not installed, you would add no-asm above and use ms\do_ms.bat 
   214          instead of the ms\do_masm.bat script.</div>
   215        </li>
   216  
   217        <li>
   218          <p>[Optional] Database libraries (for <code class="module"><a href="../mod/mod_dbd.html">mod_dbd</a></code>
   219          and <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code>)</p>
   220  
   221          <p>The apr-util library exposes dbm (keyed database) and dbd (query
   222          oriented database) client functionality to the httpd server and its
   223          modules, such as authentication and authorization.  The sdbm dbm and
   224          odbc dbd providers are compiled unconditionally.</p>
   225  
   226          <p>The dbd support includes the Oracle instantclient package, MySQL,
   227          PostgreSQL and sqlite.  To build these all, for example, set up the
   228          LIB to include the library path, INCLUDE to include the headers path,
   229          and PATH to include the dll bin path of all four SDK's, and set the
   230          DBD_LIST environment variable to inform the build which client driver
   231          SDKs are installed correctly, e.g.;</p>
   232  
   233          <div class="example"><p><code>
   234            set DBD_LIST=sqlite3 pgsql oracle mysql
   235          </code></p></div>
   236  
   237          <p>Similarly, the dbm support can be extended with DBM_LIST to
   238          build a Berkeley DB provider (db) and/or gdbm provider, by similarly
   239          configuring LIB, INCLUDE and PATH first to ensure the client library
   240          libs and headers are available.</p>
   241  
   242          <div class="example"><p><code>
   243            set DBM_LIST=db gdbm
   244          </code></p></div>
   245  
   246          <div class="note">Depending on the choice of database distributions, it may be
   247          necessary to change the actual link target name (e.g. gdbm.lib vs.
   248          libgdb.lib) that are listed in the corresponding .dsp/.mak files
   249          within the directories srclib\apr-util\dbd or ...\dbm.</div>
   250  
   251          <p>See the README-win32.txt file for more hints on obtaining the
   252          various database driver SDKs.</p>
   253        </li>
   254      </ul>
   255  
   256    </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   257  <div class="section">
   258  <h2><a name="commandbuild" id="commandbuild">Command-Line Build</a></h2>
   259  
   260      
   261  
   262      <p><code>Makefile.win</code> is the top level Apache makefile.
   263      To compile Apache on Windows, simply use one of the following commands
   264      to build the <code>release</code> or <code>debug</code> flavor:</p>
   265  
   266      <div class="example"><p><code>
   267        nmake /f Makefile.win _apacher<br /><br />
   268        nmake /f Makefile.win _apached
   269      </code></p></div>
   270  
   271      <p>Either command will compile Apache. The latter will disable
   272      optimization of the resulting files, making it easier to single
   273      step the code to find bugs and track down problems.</p>
   274  
   275      <p>You can add your apr-util dbd and dbm provider choices with the
   276      additional make (environment) variables DBD_LIST and DBM_LIST, 
   277      see the comments about [Optional] Database libraries, above.
   278      Review the initial comments in Makefile.win for additional options
   279      that can be provided when invoking the build.</p>
   280  
   281    </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   282  <div class="section">
   283  <h2><a name="workspacebuild" id="workspacebuild">Developer Studio Workspace IDE Build</a></h2>
   284  
   285      
   286  
   287      <p>Apache can also be compiled using VC++'s Visual Studio
   288      development environment. To simplify this process, a
   289      Visual Studio workspace, <code>Apache.dsw</code>, is provided.
   290      This workspace exposes the entire list of working <code>.dsp</code>
   291      projects that are required for the complete Apache binary release.
   292      It includes dependencies between the projects to assure that they
   293      are built in the appropriate order.</p>
   294  
   295      <p>Open the <code>Apache.dsw</code> workspace, and select
   296      <code>InstallBin</code> (<code>Release</code> or <code>Debug</code> build,
   297      as desired) as the Active Project. <code>InstallBin</code> causes all
   298      related project to be built, and then invokes <code>Makefile.win</code> to
   299      move the compiled executables and dlls. You may personalize the
   300      <code>INSTDIR=</code> choice by changing <code>InstallBin</code>'s Settings,
   301      General tab, Build command line entry. <code>INSTDIR</code> defaults to the
   302      <code>/Apache2</code> directory. If you only want a test compile (without
   303      installing) you may build the <code>BuildBin</code> project instead.</p>
   304  
   305      <p>The <code>.dsp</code> project files are distributed in Visual Studio 6.0
   306      (98) format. Visual C++ 5.0 (97) will recognize them. Visual Studio
   307      2002 (.NET) and later users must convert <code>Apache.dsw</code> plus
   308      the <code>.dsp</code> files into an <code>Apache.sln</code> plus
   309      <code>.msproj</code> files.  Be sure you reconvert the <code>.msproj</code>
   310      file again if its source <code>.dsp</code> file changes! This is really
   311      trivial, just open <code>Apache.dsw</code> in the VC++ 7.0 IDE once again
   312      and reconvert.</p>
   313  
   314      <div class="note">There is a flaw in the .vcproj conversion of .dsp files.  devenv.exe
   315      will mis-parse the /D flag for RC flags containing long quoted /D'efines
   316      which contain spaces.  The command:
   317      <div class="example"><p><code>
   318        perl srclib\apr\build\cvtdsp.pl -2005
   319      </code></p></div>
   320      will convert the /D flags for RC flags to use an alternate, parseable
   321      syntax; unfortunately this syntax isn't supported by Visual Studio 97
   322      or its exported .mak files.  These /D flags are used to pass the long
   323      description of the mod_apachemodule.so files to the shared .rc resource
   324      version-identifier build.</div>
   325  
   326      <p>Visual Studio 2002 (.NET) and later users should also use the Build
   327      menu, Configuration Manager dialog to uncheck both the <code>Debug</code>
   328      and <code>Release</code> Solution modules <code>abs</code>, 
   329      <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code> and <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> components, as
   330      well as every component starting with <code>apr_db*</code>.  These modules
   331      are built by invoking <code>nmake</code>, or the IDE directly with the
   332      <code>BinBuild</code> target, which builds those modules conditionally
   333      if the <code>srclib</code> directories <code>openssl</code> and/or
   334      <code>zlib</code> exist, and based on the setting of <code>DBD_LIST</code>
   335      and <code>DBM_LIST</code> environment variables.</p>
   336  
   337    </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   338  <div class="section">
   339  <h2><a name="exportingmakfiles" id="exportingmakfiles">Exporting command-line .mak files</a></h2>
   340  
   341      
   342  
   343      <p>Exported <code>.mak</code> files pose a greater hassle, but they are
   344      required for Visual C++ 5.0 users to build <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>,
   345      abs (<code class="program"><a href="../programs/ab.html">ab</a></code> with SSL support) and/or
   346      <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>.  The .mak files also support a broader
   347      range of C++ tool chain distributions, such as Visual Studio Express.</p>
   348  
   349      <p>You must first build all projects in order to create all dynamic 
   350      auto-generated targets, so that dependencies can be parsed correctly. 
   351      Build the entire project from within the Visual Studio 6.0 (98) IDE,
   352      using the <code>BuildAll</code> target, then use the Project Menu Export
   353      for all makefiles (checking on "with dependencies".)  Run the following
   354      command to correct absolute paths into relative paths so they will build
   355      anywhere:</p>
   356  
   357      <div class="example"><p><code>
   358        perl srclib\apr\build\fixwin32mak.pl
   359      </code></p></div>
   360  
   361      <p>You must type this command from the <em>top level</em>
   362      directory of the httpd source tree. Every
   363      <code>.mak</code> and <code>.dep</code> project file within
   364      the current directory and below will be corrected, and the
   365      timestamps adjusted to reflect the <code>.dsp</code>.</p>
   366  
   367      <p>Always review the generated <code>.mak</code> and <code>.dep</code>
   368      files for Platform SDK or other local, machine specific file paths.
   369      The <code>DevStudio\Common\MSDev98\bin\</code> (VC6) directory contains
   370      a <code>sysincl.dat</code> file, which lists all exceptions.  Update
   371      this file (including both forward and backslashed paths, such as both
   372      <code>sys/time.h</code> and <code>sys\time.h</code>) to ignore such
   373      newer dependencies.  Including local-install paths in a distributed 
   374      <code>.mak</code> file will cause the build to fail completely.</p>
   375  
   376      <p>If you contribute back a patch that revises project files, we
   377      must commit project files in Visual Studio 6.0 format. Changes
   378      should be simple, with minimal compilation and linkage flags that
   379      can be recognized by all Visual Studio environments.</p>
   380  
   381    </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   382  <div class="section">
   383  <h2><a name="installation" id="installation">Installation</a></h2>
   384  
   385      
   386  
   387      <p>Once Apache has been compiled, it needs to be installed in
   388      its server root directory. The default is the
   389      <code>\Apache2</code> directory, of the same drive.</p>
   390  
   391      <p>To build and install all the files into the desired folder
   392      <em>dir</em> automatically, use one of the following
   393      <code>nmake</code> commands:</p>
   394  
   395      <div class="example"><p><code>
   396        nmake /f Makefile.win installr INSTDIR=<em>dir</em><br />
   397        nmake /f Makefile.win installd INSTDIR=<em>dir</em>
   398      </code></p></div>
   399  
   400      <p>The <em>dir</em> argument to <code>INSTDIR</code> provides
   401      the installation directory; it can be omitted if Apache is
   402      to be installed into <code>\Apache22</code> (of the current
   403      drive).</p>
   404  
   405    </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   406  <div class="section">
   407  <h2><a name="projectcomponents-warn" id="projectcomponents-warn">Warning about building Apache from the development tree</a></h2>
   408  
   409      
   410  
   411      <div class="note">Note only the <code>.dsp</code> files are maintained between <code>release</code>
   412      builds. The <code>.mak</code> files are NOT regenerated, due to the tremendous
   413      waste of reviewer's time. Therefore, you cannot rely on the <code>NMAKE</code>
   414      commands above to build revised <code>.dsp</code> project files unless you
   415      then export all <code>.mak</code> files yourself from the project. This is
   416      unnecessary if you build from within the Microsoft
   417      Developer Studio environment.</div>
   418  
   419    </div></div>
   420  <div class="bottomlang">
   421  <p><span>Available Languages: </span><a href="../en/platform/win_compiling.html" title="English">&nbsp;en&nbsp;</a> |
   422  <a href="../ko/platform/win_compiling.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a></p>
   423  </div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div>
   424  <script type="text/javascript"><!--//--><![CDATA[//><!--
   425  var comments_shortname = 'httpd';
   426  var comments_identifier = 'http://httpd.apache.org/docs/2.2/platform/win_compiling.html';
   427  (function(w, d) {
   428      if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
   429          d.write('<div id="comments_thread"><\/div>');
   430          var s = d.createElement('script');
   431          s.type = 'text/javascript';
   432          s.async = true;
   433          s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
   434          (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
   435      }
   436      else { 
   437          d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
   438      }
   439  })(window, document);
   440  //--><!]]></script></div><div id="footer">
   441  <p class="apache">Copyright 2017 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
   442  <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
   443  if (typeof(prettyPrint) !== 'undefined') {
   444      prettyPrint();
   445  }
   446  //--><!]]></script>
   447  </body></html>