qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darryl L. Pierce (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)
Date Tue, 01 Oct 2013 12:40:26 GMT

    [ https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782885#comment-13782885

Darryl L. Pierce commented on PROTON-342:

I'll add a note to the README file saying that DESTDIR doesn't affect the install prefix or
anything that depends on it.

Regarding the dynamic languages, we can always provide an override variable that sets the
path(s) at CMake initialization. If this value is not present, which would be the default,
then CMake would do as it does currently and interrogate the dynamic language for the install

> 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

View raw message