[
https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782741#comment-13782741
]
Gordon Sim commented on PROTON-342:
-----------------------------------
As far as I can see it is still not possible to install both c headers/libs and
bindings to a non-standard location and still rely on pkg-config for dependency
configuration. I would concede that is not the common use case, but it is one
that I would have expected to work. For my own needs I can just disable the
bindings. If you close it mark it as wont fix (rather than not a bug or
resolved) unless you can point describe a solution.
"The dynamic languages are behaving as expected, as they will install to
directories as specified by the dynamic languages themselves."
So is there some other way to change where the bindings get installed, if I as
a user don't want to use the standard location for the given language for
whatever reason?
> 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)
