apr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jerenkra...@apache.org
Subject svn commit: r157701 - in apr/site/trunk: docs/compiling_win32.html xdocs/compiling_win32.html
Date Wed, 16 Mar 2005 06:09:05 GMT
Author: jerenkrantz
Date: Tue Mar 15 22:09:03 2005
New Revision: 157701

URL: http://svn.apache.org/viewcvs?view=rev&rev=157701
Log:
Take a pass at updating the Win32 build instructions...

Modified:
    apr/site/trunk/docs/compiling_win32.html
    apr/site/trunk/xdocs/compiling_win32.html

Modified: apr/site/trunk/docs/compiling_win32.html
URL: http://svn.apache.org/viewcvs/apr/site/trunk/docs/compiling_win32.html?view=diff&r1=157700&r2=157701
==============================================================================
--- apr/site/trunk/docs/compiling_win32.html (original)
+++ apr/site/trunk/docs/compiling_win32.html Tue Mar 15 22:09:03 2005
@@ -22,107 +22,118 @@
 
 <ul>
 
-<li>Microsoft Visual C++ 5.0 or higher.<br><br>APR can be built using
-    the command line tools, or from within the Visual Studio IDE Workbench.
-    the command line tools are configured with the vcvars32 batch file:
-<pre>
-  "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat"
-</pre>
-
-<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 
-    builds, the Platform SDK environment is prepared by the setenv batch file:
-<pre>
-  "c:\Program Files\Platform SDK\setenv.bat"
-</pre>
-    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> 
-
-<li>The awk utility (awk, gawk or similar.)<br><br>
-    To build APR, several files are modified using the awk utility.  
-    awk was chosen since it is a very small download (compared with Perl 
-    or WSH/VB) and accomplishes the task. 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 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>
+<li>A <a
+    href="http://msdn.microsoft.com/vstudio/">suitable Microsoft compiler</a>:
+    such as: Microsoft Visual C++ 5.0 or higher; Microsoft Visual Studio .NET
+    2002 or higher (with Visual C++ .NET compiler).  APR can be built using the
+    <a href="#commandline">command line tools</a>, or from within the
+    <a href="#workspace">graphical IDE</a> (Visual Studio IDE Workbench or
+    Microsoft Development Environment).  We have not yet tried the 'Express'
+    versions of Visual Studio .NET and are unable to provide support.
+</li>
+
+<li><strong>Visual C++ 5.0 users only</strong>: The Windows Platform SDK.
+    Visual C++ 5.0 developers need the updated Microsoft Windows Platform SDK
+    to enable some APR features.  The Platform SDK files distributed with
+    Visual C++ 6.0 and later are sufficient, so those users may skip this
+    requirement.  <strong>Note</strong> that the Windows Platform SDK update
+    is required to enable all supported features with MSVC++ 5.0.  Without a
+    current version, 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 too often to cite.
+</li>
+
+<li><strong>Historical APR releases only</strong>: Current versions of
APR 
+    do <strong>not</strong> need awk - however, older versions of APR (prior
+    to APR 1.1.1) <strong>require</strong> awk.  You may find a Win32 binary
+    version of awk at: <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>
+    <br /><br />
+    For Visual Studio 5.0/6.0 Graphical builds, it 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.
+    For Visual Studio .NET 2003 and newer, you may need to copy awk to the
+    Common7\Tools\Bin directory (i.e. where RC.exe is) - it no longer has
+    the specific PATH options (as far as we can tell).</li>
 
 </ul>
 
-<h3><a name="commandline">Command-Line Build</a></h3>
-
-<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>
-<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" \
-
-	msdev aprutil.dsw /MAKE \
-		"libapr - Win32 Release" \
-		"libapriconv - Win32 Release" \
-		"gen_uri_delims - Win32 Release" \
-		"xml - Win32 Release" \
-        	"libaprutil - Win32 Release" \
-
-</pre>
+<h3><a name="layout">Required Directory Layout</a></h3>
 
-<p>Either command will compile APR. The latter will build the libraries as
-   .dll dynamic shared libraries, rather than static libraries.</p>
+<p>For a supported build, you must have apr, apr-iconv, and apr-util
+   checked-out in parallel directories.  For example:</p>
 
-<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>
+<ul>
+   <li><code>C:\work\apr\</code></li>
+   <li><code>C:\work\apr-iconv\</code></li>
+   <li><code>C:\work\apr-util\</code></li>
+</ul>
 
-<h3><a name="workspace">Developer Studio Workspace IDE Build</a></h3>
+<h3><a name="workspace">Developer Studio Workspace/Microsoft Development Environment
IDE Build</a></h3>
 
-<p>APR can also be compiled using VC++'s VisualStudio development
-   environment. To simplify this process, a complete VisualStudio workspace,
-   apr-util/aprutil.dsw, is provided.  This workspace exposes the entire list 
-   of working .dsp projects that are required for the complete APR binary 
-   release.  It includes dependencies between the projects to assure that 
-   they are built in the appropriate order.</p>
+<p>APR can be compiled using Visual C++'s graphical environment.
+   To simplify this process, a complete Visual Studio workspace,
+   <code>apr-util/aprutil.dsw</code>, is provided.  This workspace exposes the
+   entire list of working .dsp projects that are required for the complete APR
+   binary release.  It includes dependencies between the projects to assure
+   that they are built in the appropriate order.</p>
+
+<p>These workspaces are shipped in the Visual Studio 6.0 format - however,
+   you can safely 'upgrade' them to your current Visual Studio release (i.e.
+   Visual Studio 2003 .NET).  However, for compatibility and simplicity, we
+   only distribute Visual Studio 6.0 workspaces.  See below for <a
+   href="convert5">converting the workspaces for Visual Studio 5.0</a>.</p>
 
 <p>Open the apr-util/aprutil.dsw workspace, and choose either aprutil or
    libaprutil (for static or dynamic libraries) with the Release or Debug
    build as the Active Project.  aprutil.dsw causes all related projects to 
    be built.</p>
 
-<p>The apr test environment can be compiled using VC++'s VisualStudio 
-   development environment with the apr/test/aprtest.dsw project.  
+<p>The apr test environment can be compiled using VC++'s Visual Studio
+   development environment with the apr/test/aprtest.dsw project.
    This workspace exposes the apr/apr.dsp static library and the 
    apr/test/aprtest.dsp projects that allow the developer to assemble the
    entire test application suite.</p>
 
-<p>The .dsp project files are distributed in Visual C++ 6.0 format.  Visual
-   C++ 5.0 (97) will recognize them.  To quickly prepare the .dsp files in 
-   the native Visual Studio 5.0 (97) format, you can run this command
-   from the top-level apr directory (above apr, apr-util and apr-iconv):
+<h3><a name="commandline">Command-Line Build</a></h3>
+
+<p>If you use the command line, you must configure it:</p>
 <pre>
-     perl apr\build\cvtdsp.pl -5
+  "C:\Program Files\DevStudio\VC\Bin\vcvars32.bat"
 </pre>
-   You must type this command from the <em>top level</em> directory of the apr
-   source tree.  Every VC6 .dsp project file within the current directory and 
-   below will be listed as it is converted.  If you contribute back a patch that
-   revises project files, please convert them back with the the -6 option instead
-   of -5, which returns the project files to Visual Studio 6.0 format.</p>
+
+<p>If necessary, you will need to prepare the Platform SDK environment:</p>
+<pre>
+  "c:\Program Files\Platform SDK\setenv.bat"
+</pre>
+
+<p>cd to the apr-util directory.  Now, 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" \
+
+  msdev aprutil.dsw /MAKE \
+    libapr - Win32 Release" \
+    libapriconv - Win32 Release" \
+    gen_uri_delims - Win32 Release" \
+    xml - Win32 Release" \
+    libaprutil - Win32 Release" \
+</pre>
+
+<p>Either command will compile APR. The latter will build the libraries as
+   .dll dynamic shared libraries, rather than static libraries.</p>
+
+<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>
 
 <h3><a name="integrating">Integrating the Library</a></h3>
 
@@ -154,15 +165,30 @@
    and apr-util symbols from being tagged as __declspec(dllimport),
    eliminating compiliation warnings and speeding up execution.</p>
 
-<p><strong>Warning about building Apache from the development tree</strong></p>
+<p><strong>Warning about building APR from the development tree</strong></p>
 
-<p>Only the .dsp files are maintained within SVN.  Win32 .mak files 
+<p><strong>For Visual Studio C++ 5.0 command line users</strong>:
+   Only the .dsp files are maintained within SVN.  Win32 .mak files
    are NOT maintained in SVN, due to the tremendous waste of
-   reviewer's time.  Therefore, you cannot rely on the NMAKE commands 
+   reviewer's time.  Therefore, you cannot rely on the NMAKE commands
    above to build revised .dsp project files unless you then export
-   all .mak files yourself from the project.  This is unnecessary if 
-   you build from within the Microsoft DeveloperStudio environment, or
-   use Visual C++ 6.0 or greater.</p>
+   all .mak files yourself from the project.</p>
+
+<h3><a name="convert5">Converting the Project for Visual C++ 5.0</a></h3>
+
+<p>The .dsp project files are distributed in Visual C++ 6.0 format.  Visual
+   C++ 5.0 (97) will recognize them.  To quickly prepare the .dsp files in 
+   the native Visual Studio 5.0 (97) format, you can run this command
+   from the top-level apr directory (above apr, apr-util and apr-iconv):</p>
+<pre>
+     perl apr\build\cvtdsp.pl -5
+</pre>
+
+<p>You must type this command from the <em>top level</em> directory of
the apr
+source tree.  Every VC6 .dsp project file within the current directory and
+below will be listed as it is converted.  If you contribute back a patch that
+revises project files, please convert them back with the the -6 option instead
+of -5, which returns the project files to Visual Studio 6.0 format.</p>
 
 </body>
 </html>

Modified: apr/site/trunk/xdocs/compiling_win32.html
URL: http://svn.apache.org/viewcvs/apr/site/trunk/xdocs/compiling_win32.html?view=diff&r1=157700&r2=157701
==============================================================================
--- apr/site/trunk/xdocs/compiling_win32.html (original)
+++ apr/site/trunk/xdocs/compiling_win32.html Tue Mar 15 22:09:03 2005
@@ -22,107 +22,118 @@
 
 <ul>
 
-<li>Microsoft Visual C++ 5.0 or higher.<br><br>APR can be built using
-    the command line tools, or from within the Visual Studio IDE Workbench.
-    the command line tools are configured with the vcvars32 batch file:
-<pre>
-  "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat"
-</pre>
-
-<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 
-    builds, the Platform SDK environment is prepared by the setenv batch file:
-<pre>
-  "c:\Program Files\Platform SDK\setenv.bat"
-</pre>
-    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> 
-
-<li>The awk utility (awk, gawk or similar.)<br><br>
-    To build APR, several files are modified using the awk utility.  
-    awk was chosen since it is a very small download (compared with Perl 
-    or WSH/VB) and accomplishes the task. 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 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>
+<li>A <a
+    href="http://msdn.microsoft.com/vstudio/">suitable Microsoft compiler</a>:
+    such as: Microsoft Visual C++ 5.0 or higher; Microsoft Visual Studio .NET
+    2002 or higher (with Visual C++ .NET compiler).  APR can be built using the
+    <a href="#commandline">command line tools</a>, or from within the
+    <a href="#workspace">graphical IDE</a> (Visual Studio IDE Workbench or
+    Microsoft Development Environment).  We have not yet tried the 'Express'
+    versions of Visual Studio .NET and are unable to provide support.
+</li>
+
+<li><strong>Visual C++ 5.0 users only</strong>: The Windows Platform SDK.
+    Visual C++ 5.0 developers need the updated Microsoft Windows Platform SDK
+    to enable some APR features.  The Platform SDK files distributed with
+    Visual C++ 6.0 and later are sufficient, so those users may skip this
+    requirement.  <strong>Note</strong> that the Windows Platform SDK update
+    is required to enable all supported features with MSVC++ 5.0.  Without a
+    current version, 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 too often to cite.
+</li>
+
+<li><strong>Historical APR releases only</strong>: Current versions of
APR 
+    do <strong>not</strong> need awk - however, older versions of APR (prior
+    to APR 1.1.1) <strong>require</strong> awk.  You may find a Win32 binary
+    version of awk at: <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>
+    <br /><br />
+    For Visual Studio 5.0/6.0 Graphical builds, it 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.
+    For Visual Studio .NET 2003 and newer, you may need to copy awk to the
+    Common7\Tools\Bin directory (i.e. where RC.exe is) - it no longer has
+    the specific PATH options (as far as we can tell).</li>
 
 </ul>
 
-<h3><a name="commandline">Command-Line Build</a></h3>
-
-<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>
-<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" \
-
-	msdev aprutil.dsw /MAKE \
-		"libapr - Win32 Release" \
-		"libapriconv - Win32 Release" \
-		"gen_uri_delims - Win32 Release" \
-		"xml - Win32 Release" \
-        	"libaprutil - Win32 Release" \
-
-</pre>
+<h3><a name="layout">Required Directory Layout</a></h3>
 
-<p>Either command will compile APR. The latter will build the libraries as
-   .dll dynamic shared libraries, rather than static libraries.</p>
+<p>For a supported build, you must have apr, apr-iconv, and apr-util
+   checked-out in parallel directories.  For example:</p>
 
-<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>
+<ul>
+   <li><code>C:\work\apr\</code></li>
+   <li><code>C:\work\apr-iconv\</code></li>
+   <li><code>C:\work\apr-util\</code></li>
+</ul>
 
-<h3><a name="workspace">Developer Studio Workspace IDE Build</a></h3>
+<h3><a name="workspace">Developer Studio Workspace/Microsoft Development Environment
IDE Build</a></h3>
 
-<p>APR can also be compiled using VC++'s VisualStudio development
-   environment. To simplify this process, a complete VisualStudio workspace,
-   apr-util/aprutil.dsw, is provided.  This workspace exposes the entire list 
-   of working .dsp projects that are required for the complete APR binary 
-   release.  It includes dependencies between the projects to assure that 
-   they are built in the appropriate order.</p>
+<p>APR can be compiled using Visual C++'s graphical environment.
+   To simplify this process, a complete Visual Studio workspace,
+   <code>apr-util/aprutil.dsw</code>, is provided.  This workspace exposes the
+   entire list of working .dsp projects that are required for the complete APR
+   binary release.  It includes dependencies between the projects to assure
+   that they are built in the appropriate order.</p>
+
+<p>These workspaces are shipped in the Visual Studio 6.0 format - however,
+   you can safely 'upgrade' them to your current Visual Studio release (i.e.
+   Visual Studio 2003 .NET).  However, for compatibility and simplicity, we
+   only distribute Visual Studio 6.0 workspaces.  See below for <a
+   href="convert5">converting the workspaces for Visual Studio 5.0</a>.</p>
 
 <p>Open the apr-util/aprutil.dsw workspace, and choose either aprutil or
    libaprutil (for static or dynamic libraries) with the Release or Debug
    build as the Active Project.  aprutil.dsw causes all related projects to 
    be built.</p>
 
-<p>The apr test environment can be compiled using VC++'s VisualStudio 
-   development environment with the apr/test/aprtest.dsw project.  
+<p>The apr test environment can be compiled using VC++'s Visual Studio
+   development environment with the apr/test/aprtest.dsw project.
    This workspace exposes the apr/apr.dsp static library and the 
    apr/test/aprtest.dsp projects that allow the developer to assemble the
    entire test application suite.</p>
 
-<p>The .dsp project files are distributed in Visual C++ 6.0 format.  Visual
-   C++ 5.0 (97) will recognize them.  To quickly prepare the .dsp files in 
-   the native Visual Studio 5.0 (97) format, you can run this command
-   from the top-level apr directory (above apr, apr-util and apr-iconv):
+<h3><a name="commandline">Command-Line Build</a></h3>
+
+<p>If you use the command line, you must configure it:</p>
 <pre>
-     perl apr\build\cvtdsp.pl -5
+  "C:\Program Files\DevStudio\VC\Bin\vcvars32.bat"
 </pre>
-   You must type this command from the <em>top level</em> directory of the apr
-   source tree.  Every VC6 .dsp project file within the current directory and 
-   below will be listed as it is converted.  If you contribute back a patch that
-   revises project files, please convert them back with the the -6 option instead
-   of -5, which returns the project files to Visual Studio 6.0 format.</p>
+
+<p>If necessary, you will need to prepare the Platform SDK environment:</p>
+<pre>
+  "c:\Program Files\Platform SDK\setenv.bat"
+</pre>
+
+<p>cd to the apr-util directory.  Now, 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" \
+
+  msdev aprutil.dsw /MAKE \
+    libapr - Win32 Release" \
+    libapriconv - Win32 Release" \
+    gen_uri_delims - Win32 Release" \
+    xml - Win32 Release" \
+    libaprutil - Win32 Release" \
+</pre>
+
+<p>Either command will compile APR. The latter will build the libraries as
+   .dll dynamic shared libraries, rather than static libraries.</p>
+
+<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>
 
 <h3><a name="integrating">Integrating the Library</a></h3>
 
@@ -154,15 +165,30 @@
    and apr-util symbols from being tagged as __declspec(dllimport),
    eliminating compiliation warnings and speeding up execution.</p>
 
-<p><strong>Warning about building Apache from the development tree</strong></p>
+<p><strong>Warning about building APR from the development tree</strong></p>
 
-<p>Only the .dsp files are maintained within SVN.  Win32 .mak files 
+<p><strong>For Visual Studio C++ 5.0 command line users</strong>:
+   Only the .dsp files are maintained within SVN.  Win32 .mak files
    are NOT maintained in SVN, due to the tremendous waste of
-   reviewer's time.  Therefore, you cannot rely on the NMAKE commands 
+   reviewer's time.  Therefore, you cannot rely on the NMAKE commands
    above to build revised .dsp project files unless you then export
-   all .mak files yourself from the project.  This is unnecessary if 
-   you build from within the Microsoft DeveloperStudio environment, or
-   use Visual C++ 6.0 or greater.</p>
+   all .mak files yourself from the project.</p>
+
+<h3><a name="convert5">Converting the Project for Visual C++ 5.0</a></h3>
+
+<p>The .dsp project files are distributed in Visual C++ 6.0 format.  Visual
+   C++ 5.0 (97) will recognize them.  To quickly prepare the .dsp files in 
+   the native Visual Studio 5.0 (97) format, you can run this command
+   from the top-level apr directory (above apr, apr-util and apr-iconv):</p>
+<pre>
+     perl apr\build\cvtdsp.pl -5
+</pre>
+
+<p>You must type this command from the <em>top level</em> directory of
the apr
+source tree.  Every VC6 .dsp project file within the current directory and
+below will be listed as it is converted.  If you contribute back a patch that
+revises project files, please convert them back with the the -6 option instead
+of -5, which returns the project files to Visual Studio 6.0 format.</p>
 
 </body>
 </html>



Mime
View raw message