Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-2827

QPID Cpp WinSDK does not contain 64-bit libraries

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.7
    • C++ Client
    • None
    • Windows

    Description

      The kit build procedure and the hard-coded kit example files support 32-bit Win32 only. This issue tracks the addition of the x64 platform.

      Attachments

        1. x64-qwip-07.patch
          208 kB
          Charles E. Rolke
        2. restore-less-than-char.patch
          0.4 kB
          Charles E. Rolke

        Activity

          Rooted at qpid/cpp, this patch restores angle bracket clobbered during manual replacement of Apache notice.

          chug Charles E. Rolke added a comment - Rooted at qpid/cpp, this patch restores angle bracket clobbered during manual replacement of Apache notice.

          Also note that a 32-bit Windows system will skip installing the Visual Studio x64 cross compiler by default. To install it re-run the Visual Studio setup. Select Change or Remove Visual Studio to get into Maintenance Mode. Choose Add or Remove Features. Under Language Tools -> Visual C++, check X64 Compilers and Tools. And there you go.

          chug Charles E. Rolke added a comment - Also note that a 32-bit Windows system will skip installing the Visual Studio x64 cross compiler by default. To install it re-run the Visual Studio setup. Select Change or Remove Visual Studio to get into Maintenance Mode. Choose Add or Remove Features. Under Language Tools -> Visual C++, check X64 Compilers and Tools. And there you go.

          Steve, right. The procedure builds two separate .zip kits, one each for 32- and 64-bit.

          chug Charles E. Rolke added a comment - Steve, right. The procedure builds two separate .zip kits, one each for 32- and 64-bit.

          Rooted at qpid\cpp this patch adds support and process for build a 64-bit WinSDK.

          • 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.
          chug Charles E. Rolke added a comment - Rooted at qpid\cpp this patch adds support and process for build a 64-bit WinSDK. 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.

          FWIW, 64-bit packages are usually separate from 32-bit packages for Windows.

          shuston Stephen D. Huston added a comment - FWIW, 64-bit packages are usually separate from 32-bit packages for Windows.

          People

            tross Ted Ross
            chug Charles E. Rolke
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: