Qpid Proton
  1. Qpid Proton
  2. PROTON-217

cmake build system should include "install" target for Java binaries

        Details

        • Type: Improvement Improvement
        • Status: Closed
        • Priority: Minor Minor
        • Resolution: Fixed
        • Affects Version/s: 0.3
        • Fix Version/s: 0.4
        • Component/s: None
        • Labels:
          None

          Description

          The cmake build system was recently modified in PROTON-194 to include compilation of the Java artefacts. However, we don't yet have a target to install them.

          Further discussion is required to decide where they should be installed.

            Issue Links

            relates to

            Improvement - An improvement or enhancement to an existing feature or task. PROTON-194 Change proton's build systems to allow for the creation of a Java binding for proton-c.

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Philip Harvey added a comment -

              this is a follow-on from the work done in PROTON-194.

              Show
              Philip Harvey added a comment - this is a follow-on from the work done in PROTON-194 .
              Hide
              Permalink
              Philip Harvey added a comment -

              The link below gives some background to how jar installation on Linux works, at least on Fedora:

              https://fedoraproject.org/wiki/Packaging:Java#JAR_file_installation

              Show
              Philip Harvey added a comment - The link below gives some background to how jar installation on Linux works, at least on Fedora: https://fedoraproject.org/wiki/Packaging:Java#JAR_file_installation
              Hide
              Permalink
              Keith Wall added a comment - - edited

              Build system changed so that 'make install' installs all JARs (and shared objects) into the install tree.

              The install locations are controlled by the following CMake variables:

              JAVA_INSTALL_DIR "Installation directory for all JARs except those using JNI" (defaults to $

              {SHARE_INSTALL_DIR}

              /java)
              JNI_INSTALL_DIR "Installation directory for all JARs utilising JNI" (defaults to $

              {LIB_INSTALL_DIR}/java)
              JNI_SHARED_LIB_INSTALL_DIR "Installation directory for shared objects used by JNI JARs" (defaults to ${LIB_INSTALL_DIR}

              )

              Variables default values are based on the fundamental install variables SHARE_INSTALL_DIR and LIB_INSTALL_DIR, so any change to the install prefix will be incorporated automatically.

              Show
              Keith Wall added a comment - - edited Build system changed so that 'make install' installs all JARs (and shared objects) into the install tree. The install locations are controlled by the following CMake variables: JAVA_INSTALL_DIR "Installation directory for all JARs except those using JNI" (defaults to $ {SHARE_INSTALL_DIR} /java) JNI_INSTALL_DIR "Installation directory for all JARs utilising JNI" (defaults to $ {LIB_INSTALL_DIR}/java) JNI_SHARED_LIB_INSTALL_DIR "Installation directory for shared objects used by JNI JARs" (defaults to ${LIB_INSTALL_DIR} ) Variables default values are based on the fundamental install variables SHARE_INSTALL_DIR and LIB_INSTALL_DIR, so any change to the install prefix will be incorporated automatically.

                People

                • Assignee:
                  Philip Harvey
                  Reporter:
                  Philip Harvey
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Development