[
https://issues.apache.org/jira/browse/DISPATCH-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated DISPATCH-1332:
----------------------------------
Attachment: opt-local-tree-full.txt
> Reconcile install directories and content
> -----------------------------------------
>
> Key: DISPATCH-1332
> URL: https://issues.apache.org/jira/browse/DISPATCH-1332
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 1.6.0
> Reporter: Chuck Rolke
> Priority: Major
> Attachments: opt-local-tree-full.txt
>
>
> An installation of qpid-proton and qpid-dispatch is created with a cmake
> install where both projects use:
> {{cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/opt/local}}
> qpid-dispatch places a 64-bit .so file in /opt/local/lib when it rightfully
> belongs in /opt/local/lib64.
> Further investigation of the install directories reveals some discrepancies
> between qpid-proton and qpid-dispatch installation hierarchies. Please see
> attached _tree_ listing. One might expect them to be symmetric where
> possible. The current arrangement is confusing and makes it unnecessarily
> difficult to use them both. Note that self tests force PATH and PYTHONPATH to
> reflect the discovered locations but the values they use are not always
> practical for simple stand-alone product usage. Using the /opt/local install
> prefix then requires a PYTHONPATH like this;
> {{/opt/local/lib/python3.7/site-packages}}
> {{/opt/local/lib64/proton/bindings/python}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
