[
https://issues.apache.org/jira/browse/PROTON-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318876#comment-14318876
]
Rafael H. Schloming commented on PROTON-808:
--------------------------------------------
I didn't mean to suggest BUILD_WITH_INSTALL_RPATH is wrong in a philosophical
sense, I was just questioning whether it would actually fix the issue. I
haven't tried it, but this is what the cmake docs say:
BUILD_WITH_INSTALL_RPATH is a boolean specifying whether to link the target
in the build tree with the INSTALL_RPATH. This takes precedence over
SKIP_BUILD_RPATH and avoids the need for relinking before installation.
My interpretation of that is that it wouldn't have any impact on the RPATH of
the binaries once installed, but will instead make the binaries in the build
tree identical to those that get installed. There seem to be a bunch of other
options that control the RPATH of installed binaries.
The link I posted has a section called "Always full RPATH" which describes a
set of cmake options that may solve the issue. I don't know much about the
security implications, but my bias would be to make it "just work" if possible.
> Binaries have their library locations stripped
> ----------------------------------------------
>
> Key: PROTON-808
> URL: https://issues.apache.org/jira/browse/PROTON-808
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Reporter: Justin Ross
>
> 1. Build proton
> 2. Install to /usr/local
> 3. Run "proton"
> -> Blows up, can't find its library
> https://paste.apache.org/gd56
> http://stackoverflow.com/questions/3352041/creating-binary-with-cmake-removes-runtime-path
> The default behavior of cmake is in my opinion wrong, and we should use the
> fix mentioned in that stackoverflow discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
