You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@apr.apache.org by wr...@apache.org on 2004/08/29 03:56:30 UTC
cvs commit: apr-site/docs compiling_win32.html
wrowe 2004/08/28 18:56:30
Modified: docs compiling_win32.html
Log:
Add several good points about VC++ 5.0 v.s. 6.0, the need for /r/n
line endings and reorganize and fix typos.
Revision Changes Path
1.2 +40 -21 apr-site/docs/compiling_win32.html
Index: compiling_win32.html
===================================================================
RCS file: /home/cvs/apr-site/docs/compiling_win32.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- compiling_win32.html 26 Sep 2003 04:00:22 -0000 1.1
+++ compiling_win32.html 29 Aug 2004 01:56:30 -0000 1.2
@@ -28,6 +28,10 @@
<pre>
"c:\Program Files\DevStudio\VC\Bin\vcvars32.bat"
</pre>
+ <strong>Note:</strong> only the .zip distribution file can be used for command
+ line builds under Visual C++ 5.0, the .tar.gz files don't contain exported
+ .mak versions of the .dsp project files, and Visual C++ 6.0 is the first
+ version which is capable of .dsp based builds from the command line.</p>
<li>The Windows Platform SDK.<br><br>Visual C++ 5.0 need the updated Microsoft
Windows Platform SDK to enable some APR features. For command line
@@ -38,11 +42,11 @@
The Platform SDK files distributed with Visual C++ 6.0 and later are
sufficient, so those users may skip this requirement.<br><br>
- <strong>Note</strong> that the Windows
- Platform SDK update is required to enable all supported features.
- Without a recent update, APR will issue warnings under MSVC++ 5.0
- or fail to build entirely. Look for the update on Microsoft's website,
- we are afraid they change the link to often to cite.</p>
+ <strong>Note:</strong> The Windows Platform SDK update is required
+ to enable all supported features. Without a recent update, APR will
+ issue warnings under MSVC++ 5.0 or fail to build entirely. Look for
+ the update on Microsoft's website. (Unfortunately they change the link
+ too often to cite here.)</p>
<li>The awk utility (awk, gawk or similar.)<br><br>
To build APR, several files are modified using the awk utility.
@@ -52,10 +56,15 @@
>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 should name awk.exe rather than awk95.exe.<br>
- Note that Developer Studio IDE will only find awk.exe from the
- <u>T</u>ools menu <u>O</u>ptions... Directories settings for the
- Executable files. Add the path for awk.exe to this list, as needed.</p>
+ which you should name awk.exe rather than awk95.exe.</p>
+
+ <strong>Note:</strong> The Developer Studio IDE will only find awk.exe
+ from the <u>T</u>ools menu <u>O</u>ptions... Directories settings for the
+ Executable files, or the system path. Add the path for awk.exe
+ as needed.</p>
+
+ <strong>Note:</strong> The .zip distributions of apr contain the
+ awk-generated files, while the .tar (.gz & .Z) distributions do not.</p>
</ul>
@@ -64,24 +73,27 @@
<p>First, unpack the APR distribution into an appropriate
directory. The directory will contain the apr, apr-iconv and apr-util
directories. Open a command-line prompt and cd to the apr-util
- directory. Simply use one of the following commands to compiled the
- static or dynamic libraries, respectively, on Visual C++ 6.0 or later:</p>
+ directory.</p>
+
+<p>If you obtained the .zip distribution, the files have \r\n (CR/LF) line
+ endings. The .tar (.gz & .Z) distribtions do not, the contents must be
+ unpacked as DOS Text, otherwise use the following command from the working
+ directory containing apr, apr-iconv and apr-uilt to convert the files to text:
+<pre>
+ perl apr\build\lineends.pl apr apr-iconv apr-util
+</pre>
+<p>Then, from the apr-util working directory, simply use one of the following commands to compile the static or dynamic libraries, respectively, on
+Visual C++ 6.0 or later:</p>
<pre>
msdev aprutil.dsw /MAKE \
- "apriconv - Win32 Release" \
"apr - Win32 Release" \
- "libapr - Win32 Release" \
- "gen_uri_delims - Win32 Release" \
- "xml - Win32 Release" \
- "aprutil - Win32 Release" \
+ "apriconv - Win32 Release" \
+ "aprutil - Win32 Release"
msdev aprutil.dsw /MAKE \
"libapr - Win32 Release" \
"libapriconv - Win32 Release" \
- "gen_uri_delims - Win32 Release" \
- "xml - Win32 Release" \
- "libaprutil - Win32 Release" \
-
+ "libaprutil - Win32 Release"
</pre>
<p>Either command will compile APR. The latter will build the libraries as
@@ -89,7 +101,9 @@
<p>Replace <code>Release</code> with <code>Debug</code> to include debugging
information in the resulting files, making it easier to find bugs and
- track down problems.</p>
+ track down problems. Note that corresponding debugging .pdb files are
+ created for the <code>Release</code> builds, but due to optimizations
+ they are sometimes less than helpful.</p>
<h3><a name="workspace">Developer Studio Workspace IDE Build</a></h3>
@@ -165,4 +179,9 @@
use Visual C++ 6.0 or greater.</p>
</body>
+</html>
+. This is unnecessary if you build from
+ within the Microsoft DeveloperStudio environment, or use Visual C++ 6.0 or
+ greater.</p>
+ </body>
</html>