[
https://issues.apache.org/jira/browse/QPIDIT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702352#comment-15702352
]
Chuck Rolke commented on QPIDIT-55:
-----------------------------------
Yes that works. I can use a command line like:
{noformat}
cmake -DCMAKE_INSTALL_PREFIX=/opt/local -DPROTON_INSTALL_DIR=/opt/local ..
{noformat}
It is not satisfying to specify /opt/local twice like that. Using the Qpid
cmake scheme the PROTON_INSTALL_DIR part could be disposed. Using the Qpid
cmake scheme any proton installation could be located with:
{noformat}
cmake -DCMAKE_INSTALL_PREFIX=/opt/local
-DProton_DIR=/usr/local/qpid-proton/lib/cmake/Proton ..
{noformat}
Also, using the Qpid cmake scheme the Proton release version numbers become
visible in cmake. QPID IT builds could automatically adjust as new Proton
versions become available. Specifically the list of C++ tests to run could be
variable based on the Proton version.
> Proton install dir is hard coded into cmake
> -------------------------------------------
>
> Key: QPIDIT-55
> URL: https://issues.apache.org/jira/browse/QPIDIT-55
> Project: Apache QPID IT
> Issue Type: Bug
> Components: Installation
> Reporter: Chuck Rolke
> Assignee: Kim van der Riet
>
> Recent commits in cmake force proton to be at /usr/local. This does not work
> for me.
> We should swipe qpid-cpp/amqp code and consume proton the same way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
