[
https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783031#comment-13783031
]
Gordon Sim commented on PROTON-342:
-----------------------------------
"The use of DESTDIR does not affect the contents of libqpid-proton.pc." is not
as clear as it might be. I think something like "The paths in libqpid-proton.pc
are not adjusted for DESTDIR, so if that is specified they will not be
accurate."
> 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: Darryl L. Pierce
>
> 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
(v6.1#6144)
