summaryrefslogtreecommitdiff
path: root/cpp
diff options
context:
space:
mode:
authorTed Ross <tross@apache.org>2010-06-14 19:33:25 +0000
committerTed Ross <tross@apache.org>2010-06-14 19:33:25 +0000
commit8907175e90904c52d68f93ae967a0e12eb776110 (patch)
tree15825ab35981e60b50e6837ec5cd424963ee85eb /cpp
parent6f7cbb8bd581daf1500bc803ffd6abb96a157df3 (diff)
downloadqpid-python-8907175e90904c52d68f93ae967a0e12eb776110.tar.gz
QPID-2667 - Documentation update from Chuck Rolke
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@954603 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'cpp')
-rw-r--r--cpp/INSTALL-WINDOWS17
1 files changed, 9 insertions, 8 deletions
diff --git a/cpp/INSTALL-WINDOWS b/cpp/INSTALL-WINDOWS
index 0b09572816..195fc303d8 100644
--- a/cpp/INSTALL-WINDOWS
+++ b/cpp/INSTALL-WINDOWS
@@ -69,17 +69,18 @@ installation. The Visual Studio projects refer to it. For example:
3. Building from a Source Distribution
======================================
-The Qpid client/broker, examples, and tests are built with separate
-Visual Studio solution files. The procedure for all three is the same.
+The Qpid client/broker, examples, and tests are built with a single
+Visual Studio solution file which is generated by CMake.
-Start the Visual Studio IDE and open the desired solution. They are located
-under the distribution directory in the following places:
+From a command prompt:
-- broker/client: src/qpidc.sln
-- examples: src/examples/examples.sln
-- tests: src/tests/tests.sln
+ # cd qpid\cpp
+ # cmake -i
-Open the desired solution, select Debug or Release, and build.
+Output from CMake includes .h files in the include directory, .vcproj
+files for executables and dlls, and the qpid-cpp.sln solution file.
+
+Open the qpid-cpp.sln solution, select Debug or Release, and build.
You can build both Release and Debug from the same project.
If you build all the projects you can then "Build" the RUN_TESTS project.