[ 
https://issues.apache.org/jira/browse/PROTON-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737597#comment-14737597
 ] 

Alan Conway commented on PROTON-990:
------------------------------------

Fixed, not sure why this commit comment was not automatically included but here 
it is:

commit 6980703c47263b9910a84411705ef2a7d6a59e90
Author: Alan Conway <acon...@redhat.com>
Commit: Alan Conway <acon...@redhat.com>

    PROTON-990 [C++ binding] Examples fail to link in Visual Studio 2012, 2015
    
    Function return value types (PN_UNIQUE_PTR) were dependent on 
compile-settings, possible to
    inconsistent settings between examples and library caused link failures. 
Replaced with a stable
    return type (pn_unique_ptr) that converts to std::unique_ptr and 
std::auto_ptr.


> [C++ binding] Examples fail to link in Visual Studio 2012, 2015
> ---------------------------------------------------------------
>
>                 Key: PROTON-990
>                 URL: https://issues.apache.org/jira/browse/PROTON-990
>             Project: Qpid Proton
>          Issue Type: Bug
>    Affects Versions: 0.10
>         Environment: Windows Visual Studio 2012, 2015
>            Reporter: Chuck Rolke
>
> Issue reported by Clemens Vasters
> Trying to build current qpid-proton master on Windows with Visual Studio 2015 
> (MSVC 19) and I'm getting linker errors for std::auto_ptr for all the 
> examples in examples/cpp
> The errors all look largely the same and are all about auto_ptr, so I just 
> give one:
> {noformat}
> sync_client.obj : error LNK2019: unresolved external symbol 
> "__declspec(dllimport) public: static class std::auto_ptr<class 
> proton::message> __cdecl proton::message::create(void)" 
> (__imp_?create@message@proton@@SA?AV?$auto_ptr@Vmessage@proton@@@std@@XZ) 
> referenced in function "public: __thiscall 
> proton::message_value::message_value(void)" (??0message_value@proton@@QAE@XZ)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to