svn commit: r828098 - /qpid/trunk/qpid/cpp/INSTALL-WINDOWS

[sh...@apache.org]

Author: shuston
Date: Wed Oct 21 16:42:12 2009
New Revision: 828098

URL: http://svn.apache.org/viewvc?rev=828098&view=rev
Log:
Fix repository location and update CMake-based build instructions

Modified:
    qpid/trunk/qpid/cpp/INSTALL-WINDOWS

Modified: qpid/trunk/qpid/cpp/INSTALL-WINDOWS
URL: http://svn.apache.org/viewvc/qpid/trunk/qpid/cpp/INSTALL-WINDOWS?rev=828098&r1=828097&r2=828098&view=diff
==============================================================================
--- qpid/trunk/qpid/cpp/INSTALL-WINDOWS (original)
+++ qpid/trunk/qpid/cpp/INSTALL-WINDOWS Wed Oct 21 16:42:12 2009
@@ -82,7 +82,8 @@
 Open the desired solution, select Debug or Release, and build.
 You can build both Release and Debug from the same project.
 
-How to easily test????
+If you build all the projects you can then "Build" the RUN_TESTS project.
+This will run the test suite against the Qpid version just built.
 
 
 4. Building a Repository Working Copy
@@ -92,7 +93,7 @@
 
 To get the source code from the subversion repository (trunk) do:
 
- C:\qpid> svn checkout https://svn.apache.org/repos/asf/incubator/qpid/trunk
+ C:\qpid> svn checkout https://svn.apache.org/repos/asf/qpid/trunk
 
 The first step in the build is to configure and generate the Visual
 Studio projects. This step also generates a significant number of source
@@ -104,7 +105,7 @@
   where the source is located (C:\qpid\trunk\qpid\cpp) and one for where you
   wish to place the build. A directory separate from the source directory is
   generally preferred; it can be, but need not be, a subdirectory to the
-  source. (C:\qpid\trunk\qpid\cpp\build)
+  source. (C:\qpid\build)
 - The first time you run CMakeSetup it will ask you to select a generator.
   You should select the method you prefer to build with: Visual Studio 2008
   or NMake Makefiles.
@@ -137,10 +138,10 @@
 UML-esque dependency diagrams that are ''extremely'' useful in navigating
 around the code, especially for newcomers.
 
-There's no Windows script for generating the Doxygen documentation. You
-can either obtain the documentation in a source distribution or, if you
-are using a repository working copy, you will need to generate it on
-Linux. To try it out "make doxygen" then open doxygen/html/index.html.
+The user-level API documentation can be generated by building the
+user-api-docs project from the generated Visual Studio solution. The
+documentation is generated into the docs/api/html directory under your
+build directory.
 
 
 7. Troubleshooting



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org