[
https://issues.apache.org/jira/browse/QPID-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494137#comment-14494137
]
Jakub Scholz commented on QPID-6486:
------------------------------------
Yes, I have built the Proton libraries separately. I was simply following the
README file and it worked without problems. Then I had to first point the Qpid
CMake to the Proton binaries using the PROTON_DIR environment variable and
second I had to fix the amqp and qpidmessaging projects in Visual Studio before
building, because the paths to the headers and libraries were wrong (missing).
Without these, the qpidmessaging project doesn't build and without the
qpidmessaging project most of the other projects in qpid-cpp solution will fail
(maybe that is what you already saw).
> QPID .NET Client
> ----------------
>
> Key: QPID-6486
> URL: https://issues.apache.org/jira/browse/QPID-6486
> Project: Qpid
> Issue Type: Bug
> Environment: Windows 8 / Visual Studio 2013
> Reporter: Nathan Lusher
>
> I am trying to build a C# .NET solution that will send and receive messages
> to and from a QPID broker. There are some very simple C# examples available
> that reference the Org.Apache.Qpid.Messaging namespace.
> The issue has been trying to build the components (and all of their
> dependencies) so that I can build the Org.Apache.Qpid.Messaging.dll that I
> need to reference to build my code.
> I have followed every guide I can find, have installed cmake, boost, ruby,
> python, etc. and have slowly progressed through the cmake errors. I am,
> however, still unable to create the Org.Apache.Qpid.Messaging.sln in order to
> build the Org.Apache.Qpid.Messaging.dll, after 3 days of trying.
> Can anyone offer any advice as I feel I must be doing something wrong for it
> to be taking this long just to get a reference DLL.
> I look forward to hearing from you.
> Nathan.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
