You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2018/06/25 16:06:00 UTC
[jira] [Updated] (PROTON-342) installing into custom location
doesn't work nicely (and is not properly documented)
[ https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated PROTON-342:
-------------------------------
Fix Version/s: (was: proton-c-0.24.0)
> installing into custom location doesn't work nicely (and is not properly documented)
> ------------------------------------------------------------------------------------
>
> Key: PROTON-342
> URL: https://issues.apache.org/jira/browse/PROTON-342
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.4
> Reporter: Gordon Sim
> Assignee: Justin Ross
> Priority: Major
> Labels: docs
>
> The README suggests setting -DCMAKE_INSTALL_PREFIX when running cmake, it does not mention setting DESTDIR when invoking make install.
> If you don't set the DESTDIR on make install it will honour the CMAKE_INSTALL_PREFIX for some parts of the installation (e.g. header files, native libraries, pkg-config file etc) but the python bindings (and I assume other bindings) will still install in the standard location which will fail if you are not running as root.
> However if you set DESTDIR then this alters the location of the headers, libraries and pkg-config , which now install into $DESTDIR/$CMAKE_INSTALL_PREFIX and the pkg-config file no longer has the correct include or library paths in it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org