[DISPATCH-1332] Reconcile install directories and content

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.6.0
• Component/s: Tools
• Assignee: Unassigned
• Reporter: Charles E. Rolke
• Created: 07/May/19 16:14
• Updated: 29/Aug/21 10:05

Description

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

 

Issue Links

• duplicates: DISPATCH-1364 "make install" does not install qpid_dispatch[_site.py] files in the correct location
• is fixed by: DISPATCH-2178 Do not build separate libqpid-dispatch.so