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

Ceyron Hawthorne commented on QPIDJMS-190:
------------------------------------------

how do I get access to the users mailing list

> Issue when using CMake to install Qpid broker
> ---------------------------------------------
>
>                 Key: QPIDJMS-190
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-190
>             Project: Qpid JMS
>          Issue Type: Bug
>         Environment: Windows 7
>            Reporter: Ceyron Hawthorne
>              Labels: build
>
> I'm currently going through the process of installing the Qpid broker on 
> Windows. I've already installed cmake, boost, and python and I've added the 
> environmnet variable for the root of the Boost directory. I'm now at the step 
> where Qpid client is to be build from a source distribution (Visual Studio 
> 12). After having changed into the directory qpid\cpp I ran the command: 
> cmake -G "Visual Studio 12 2013". Toward the end of the log, I got the error:
> CMake Error at CMakeLists.txt:73 (install):
>   install FILES given no DESTINATION!
> So I checked the CMakeLists.txt file and saw that lines 73 - 76 have:
> install (FILES ${CMAKE_CURRENT_SOURCE_DIR}/README.txt
>          DESTINATION ${QPID_INSTALL_EXAMPLESDIR}
>          COMPONENT ${QPID_COMPONENT_EXAMPLES})
> I think the problem could be related to the fact that EXAMPLESDIR is being 
> used but the INSTALL_WINDOWS text file instructs you to go into the cpp 
> directory which is located in examples (the full path is: 
> qpid-cpp-0.34/bindings/qmf2/examples/cpp/)
> This is the first time I've had to work with qpid or messaging brokers so I 
> have a limited understanding of what's going on here. What destination should 
> I be providing for the install files?



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to