Bug 1152686

Summary: qpid-winsdk should support Microsoft Visual Studio 2012
Product: Red Hat Enterprise MRG Reporter: Chuck Rolke <crolke>
Component: qpid-sdkAssignee: Chuck Rolke <crolke>
Status: CLOSED ERRATA QA Contact: Jiri Prajzner <jprajzne>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 3.0CC: crolke, iboverma, jprajzne, jross, mcressma, pematous, zkraus
Target Milestone: 3.2Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-cpp-win-3.32.1.1-1 Doc Type: Enhancement
Doc Text:
Feature: +qpid-winsdk+ now supports Microsoft Visual Studio (VS) 2012, which now means Visual Studio 2008, 2010, 2012 are supported for +qpid-winsdk+. Information about the correct files to consume from +qpid-winsdk+ can be found in the _Messaging Programming Reference_ Guide's _C++ on Windows_ section. This section has been improved to describe the correct directory structure of the download binaries, and provides steps to correct consume the contents of the binaries for environments with an established (VS) environment.
Story Points: ---
Clone Of: Environment:
MPR: Some minor changes required to how we tell customers to use the VS binaries.
Last Closed: 2015-10-08 13:09:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chuck Rolke 2014-10-14 17:13:18 UTC
Description of problem:

Builds are produced with Visual Studio 2008 and 2010. This limits client applications to building with those versions. Customers may like to build with Visual Studio 2012, 2013, or even "14" which is in tech preview.

At issue with using older WinSDK kits with newer Visual Studio development systems is the underlying MSVC runtime library use. 

  Visual Studio     Run time
  -------------     --------
   2008             msvc  9
   2010             msvc 10
   2012             msvc 11
   2013             msvc 12

For example, a WinSDK linked with VS2010 uses MSVC 10 run time libraries. If this WinSDK is linked into a customer project built with VS2012 then the WinSDK still uses MSVC 10 run time while the rest of the project will use MSVC 11. Running two MSVC run time libraries in the same executable is a bad practice.

Version-Release number of selected component (if applicable):

3.0

How reproducible:

100%

Steps to Reproduce:
1. None required. The WinSDK kits do not exist.
2.
3.

Actual results:

No WinSDK for Visual Studio 2012, 2013

Expected results:

WinSDK kits for Visual Studio 2012, 2013

Additional info:

Support for this work has been committed upstream.

Comment 7 Jiri Prajzner 2015-07-01 08:30:54 UTC
Verified. qpid-winsdk supports Microsoft Visual Studio 2012.

Comment 11 Chuck Rolke 2015-07-20 15:26:13 UTC
Fine by me.

Comment 13 errata-xmlrpc 2015-10-08 13:09:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-1879.html