Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-342

installing into custom location doesn't work nicely (and is not properly documented)

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: proton-0.4
    • Fix Version/s: None
    • Component/s: proton-c
    • Labels:

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jross Justin Ross
                Reporter:
                gsim Gordon Sim
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: