[jira] [Updated] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)

2016-01-07 Thread Justin Ross (JIRA)

 [ 
https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-342:
---
Assignee: (was: Darryl L. Pierce)

> 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
>
> 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.3.4#6332)


[jira] [Updated] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)

2013-09-03 Thread Rafael H. Schloming (JIRA)

 [ 
https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael H. Schloming updated PROTON-342:
---

Fix Version/s: (was: 0.5)

 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 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