You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by wr...@apache.org on 2007/12/16 09:54:20 UTC

svn commit: r604581 - /httpd/mod_ftp/trunk/README-FTP

Author: wrowe
Date: Sun Dec 16 00:54:19 2007
New Revision: 604581

URL: http://svn.apache.org/viewvc?rev=604581&view=rev
Log:
Flesh out the readme for the 0.9.0 package

Modified:
    httpd/mod_ftp/trunk/README-FTP

Modified: httpd/mod_ftp/trunk/README-FTP
URL: http://svn.apache.org/viewvc/httpd/mod_ftp/trunk/README-FTP?rev=604581&r1=604580&r2=604581&view=diff
==============================================================================
--- httpd/mod_ftp/trunk/README-FTP (original)
+++ httpd/mod_ftp/trunk/README-FTP Sun Dec 16 00:54:19 2007
@@ -6,11 +6,12 @@
     make install
 
 If apxs is not in your path, or you are building to a different
-httpd installation, use
+httpd installation, either set the APXS environment variable, or
+the syntax;
 
     APXS=/path/to/bin/apxs ./configure.apxs
 
-instead, so the right configuration is picked up.
+so the desired configuration is picked up.
 
 To build static, or as a DSO but within the same build as httpd,
 copy the entire ftp directory over an existing httpd source tree,
@@ -33,32 +34,38 @@
 
     devenv /useenv mod_ftp.dsw
 
-The later command will convert mod_ftp.dsw to mod_ftp.sln, so
-after converting once, invoke 'devenv /useenv mod_ftp.sln' instead.
+The later command is needed on Visual Studio 2002 and later, and converts
+mod_ftp.dsw to mod_ftp.sln, so after converting once, invoke 
+
+    devenv /useenv mod_ftp.sln
+
+
 
 To regenerate the html.en documentation, here again it's as simple
 as copying the content docs/ into an httpd/docs/ tree and regenerating
-httpd's documentation.  However, it's more likely you'll be generating
-a local copy for reference in mod_ftp's tree.
+httpd's documentation.  However, it's also possible you are generating
+a local copy for reference in mod_ftp's tree, in that case you must
+have a copy of the httpd docs/manual/style.  For example;
 
     cd docs/manual
     svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/manual/style
-    svn co http://svn.apache.org/repos/asf/httpd/docs-build/trunk build
 
-        -and then...-
+In either case;
 
+    cd docs/manual
+    svn co http://svn.apache.org/repos/asf/httpd/docs-build/trunk build
     cd build
-    ./build.sh
+
+    ./build.sh all
 
         -or on windows...-
 
-    cd build
-    build.bat
+    build.bat all
 
 The same rules about an installed, locatable JAVA_HOME apply to building
 mod_ftp docs as apply to httpd.
 
 The advantage to building in-tree within httpd is that you gain the complete
-directive reference applicable to all httpd and mod_ftp directives.
+directive cross references applicable to all httpd and mod_ftp directives.