From 4214ec3e632be1f9a8cb1553280c5948fa9161bb Mon Sep 17 00:00:00 2001 From: "Stephen D. Huston" Date: Wed, 21 Oct 2009 16:42:12 +0000 Subject: Fix repository location and update CMake-based build instructions git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@828098 13f79535-47bb-0310-9956-ffa450edef68 --- cpp/INSTALL-WINDOWS | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'cpp') diff --git a/cpp/INSTALL-WINDOWS b/cpp/INSTALL-WINDOWS index 43d953aa9e..0b09572816 100644 --- a/cpp/INSTALL-WINDOWS +++ b/cpp/INSTALL-WINDOWS @@ -82,7 +82,8 @@ under the distribution directory in the following places: 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 @@ work. This directory will be referred to below as C:\qpid. 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 @@ files that are part of the build. 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 @@ Even even if the code is completely uncommented, doxygen generates 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 -- cgit v1.2.1