Gordon Sim commented on PROTON-342:

The problem can be mitigated by specifying -DBUILD_PYTHON=OFF -DBUILD_RUBY=OFF 
etc when running cmake. This prevents the building and installation of the 
bindings (and thus avoids having to use DESTDIR at all)
> 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
>             Fix For: 0.5
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to