X-Git-Url: https://granicus.if.org/sourcecode?a=blobdiff_plain;f=docs%2Fmanual%2Fplatform%2Fwin_compiling.html.en;h=112b7bc6521c48df1065981ea60ad31410fc10a8;hb=f0348fc28341bfdcce16cbf8c7d736de12ff85da;hp=36b2f0e9476f92ce97a7ec124f12f3543e31d4a1;hpb=aeff28fc12a1539222a49a606c47f6293c1cd5e8;p=apache diff --git a/docs/manual/platform/win_compiling.html.en b/docs/manual/platform/win_compiling.html.en index 36b2f0e947..112b7bc652 100644 --- a/docs/manual/platform/win_compiling.html.en +++ b/docs/manual/platform/win_compiling.html.en @@ -1,22 +1,24 @@ - -Compiling Apache for Microsoft Windows - Apache HTTP Server +Compiling Apache for Microsoft Windows - Apache HTTP Server Version 2.5 - +
<-
Apache > HTTP Server > Documentation > Version 2.5 > Platform Specific Notes

Compiling Apache for Microsoft Windows

@@ -27,20 +29,24 @@

There are many important points to consider before you begin compiling - Apache. See Using Apache with Microsoft - Windows before you begin.

+ Apache HTTP Server (httpd). See Using Apache HTTP + Server on Microsoft Windows before you begin.

+ +

httpd can be built on Windows using a cmake-based build system or with + Visual Studio project files maintained by httpd developers. The cmake-based + build system directly supports more versions of Visual Studio but currently + has considerable functional limitations.

-
+

See also

top
-

Requirements

+

Building httpd with the included Visual Studio project files

+ + +

Requirements

@@ -249,9 +255,39 @@ -
top
-
-

Command-Line Build

+ + +

Building from Unix sources

+ + + +

The policy of the Apache HTTP Server project is to only release Unix sources. + Windows source packages made available for download have been supplied by + volunteers and may not be available for every release. You can still build + the server on Windows from the Unix source tarball with just a few additional + steps.

+ +
    +
  1. Download and unpack the Unix source tarball for the latest version.
  2. +
  3. Download and unpack the Unix source tarball for latest version of + APR, AR-Util and APR-Iconv, place these sources in directories httpd-2.x.x\srclib\apr, httpd-2.x.x\srclib\apr-util and httpd-2.x.x\srclib\apr-iconv
  4. +
  5. Open a Command Prompt and CD to the httpd-2.x.x folder
  6. +
  7. Run the line endings conversion utility at the prompt;
  8. +
+ +

+ perl srclib\apr\build\lineends.pl +

+ +

You can now build the server with the Visual Studio 6.0 development + environment using the IDE. Command-Line builds of the server are not + possible from Unix sources unless you export .mak files as explained + below. +

+ + + +

Command-Line Build

@@ -274,9 +310,9 @@ Review the initial comments in Makefile.win for additional options that can be provided when invoking the build.

-
top
-
-

Developer Studio Workspace IDE Build

+ + +

Developer Studio Workspace IDE Build

@@ -330,9 +366,9 @@ zlib exist, and based on the setting of DBD_LIST and DBM_LIST environment variables.

-
top
-
-

Exporting command-line .mak files

+ + +

Exporting command-line .mak files

@@ -374,9 +410,9 @@ should be simple, with minimal compilation and linkage flags that can be recognized by all Visual Studio environments.

-
top
-
-

Installation

+ + +

Installation

@@ -398,9 +434,9 @@ to be installed into \Apache22 (of the current drive).

-
top
-
-

Warning about building Apache from the development tree

+ + +

Warning about building Apache from the development tree

@@ -412,32 +448,57 @@ unnecessary if you build from within the Microsoft Developer Studio environment.
+ +
top
+
+

Building httpd with cmake

+ + +

The primary documentation for this build mechanism is in the + README.cmake file in the source distribution. Refer to that file + for detailed instructions.

+ +

Building httpd with cmake requires building APR and APR-util separately. + Refer to their README.cmake files for instructions.

+ +

The primary limitations of the cmake-based build are inherited from the APR-util + project, and are listed below because of their impact on httpd:

+ + +

Available Languages:  en  |  ko 

-
top

Comments

This section is experimental!
Comments placed here should not be expected -to last beyond the testing phase of this system, nor do we in any way guarantee that we'll read them.
+
top

Comments

Notice:
This is not a Q&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 mailing lists.