QPID-2827 - QPID Cpp WinSDK does not contain 64-bit libraries

Patch from Chuck Rolke

* Adds the x64 platform to the cpp\example solution and six example projects. 
* Adds the x64 platform to the qpid messaging .NET binding dlls and examples. 
* Adds QPID_BUILD_ROOT environment variable to .NET binding projects for locating C++ libraries and headers, and for storing generated output. This is required to compensate for the varying location of cmake-generated directories. For a given build QPID_BUILD_ROOT must be set to the directory in which cmake was run. 
* Reorganize the bld-winsdk.ps1 script to build x86 (Win32) and x64 platforms. 
* Update Readme-winsdk.txt content. Also switch this file to DOS line endings to improve its usability on a Windows system. 
* Add a shadow solution file and shadow project files for the C# examples. The new build process copies the development example source tree to get the example sources organized into a hierarchy and then overlays the copied tree with the shadow .sln and .csproj files. Users then build the examples directly using the customized solution.


git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@990917 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 17 insertions, 50 deletions

diff --git a/qpid/cpp/README-winsdk.txt b/qpid/cpp/README-winsdk.txt
index 76d5f56681..2928894d3f 100644
--- a/qpid/cpp/README-winsdk.txt
+++ b/qpid/cpp/README-winsdk.txt
@@ -16,6 +16,12 @@ Qpid-Cpp-Win-Sdk is a software development kit for users who wish
 to write code using the Qpid-Cpp program libraries in a Windows
 environment.
 
+This kit is distributed as two zip files:
+    qpid-cpp-x86-<version>.zip - projects and libraries for 32-bit
+                                 x86 and Win32 development.
+    qpid-cpp-x64-<version>.zip - projects and libraries for 64-bit
+                                 x64 development.
+
 For additional software or information on the Qpid project go to:
 http://cwiki.apache.org/qpid/
 
@@ -58,8 +64,8 @@ The kit directories hold the content described here.
     to demonstrate using this SDK in C++.
 
   \dotnet_examples
-    A set of example source files written in C#, Visual Basic, and
-    PowerShell.
+    A Visual Studio solution file and associated project files 
+    to demonstrate using this SDK in C#.
 
   \management
     A python scripting code set for generating QMF data structures.
@@ -71,59 +77,20 @@ The kit directories hold the content described here.
 4. Building dotnet_examples
 ===========================
 
-Each file in the \dotnet_examples directory is a stand-alone, main
-console program that illustrates some facet of programming the Qpid 
-Messaging API. Use the following steps to create a project that
-builds and executes an example csharp program.
-
-A. Assume that the WinSdk was downloaded to d:\winsdk.
-B. Start Visual Studio
-C. Add File->New->Project...
-   1. Select C#, Console Application
-   2. Name: csharp.direct.receiver
-   3. Location: D:\winsdk\dotnet_examples
-   4. Check: "Create directory for solution"
-   5. Press OK
-D. In Solution Explorer
-   1. Delete program.cs
-   2. Add->Existing Item. 
-      Select d:\winsdk\dotnet_examples\csharp.direct.receiver.cs
-   3. Add Reference to d:\winsdk\bin\org.apache.qpid.messaging.dll
-      Note: In each source file a 'using' statement selects
-      Org.Apache.Qpid.Messaging, Org.Apache.Qpid.Messaging.Sessionreceiver,
-      or both. Resolve these statements with references to the files
-      in \bin.
-   4. Right-click the project and select Properties
-      Select the Build tab.
-      Select Configuration pulldown entry "All Configurations"
-      Set the Output Path to "d:\winsdk\bin"
-E. Right-click the solution and select Configuration Manager
-   1. Select Configuration -> Debug
-   2. Select Platform -> <new>
-      pick x86, OK
-F. In the standard toolbar verify that
-   1. Configuration selects Debug
-   2. Platform selects x86
-G. Build the solution.
-   1. The solution should build with no errors or warnings.
-H. Verify that the solution placed the executables in the proper place:
-   1. Directory d:\winsdk\bin has files csharp.direct.receiver.exe,  
-      csharp.direct.receiver.pdb, and csharp.direct.receiver.vshost.exe.
-
-The solution is now ready to execute. You may set breakpoints in the
-Visual Studio source file or run the executable directly from 
-d:\winsdk\bin.
-
-This process may be repeated for each example csharp source file. A similar
-process is followed for the Visual Basic example. The PowerShell example
-is executed directly in a PowerShell window.
+From the \dotnet_examples directory launch the winsdk_dotnet_examples.sln
+solution file. In the platform pulldown list select "x86" or "x64" to
+match the development kit you are using. Then build the solution in the
+Debug configuration.
+
+The resulting executable programs may be run from within Visual Studio
+or stand-alone from the \bin directory.
 
 5. Notes
 ========
-* The Qpid-Cpp binaries are produced for the 32-bit Win32 platform.
-
 * Only the Release variant of Qpid code uses the redistributable 
   MSVC90 libraries in the /bin directory. Users who wish to link to 
   the Debug variant of Qpid code may do so under their own copy of 
   Visual Studio 2008 where the debug versions of MSVC90 runtime 
   libraries are available.
+
+* The dotnet_examples are only available in the Debug configuration.