Qpid
  1. Qpid
  2. QPID-3362

Creates the Qpid gem file for distribution on RubyGems.org

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.13
    • Component/s: Ruby Client
    • Labels:
      None

      Description

      Provides the Rakefile file for creating the gem, Cmake targets for both copying the Swig wrapper code and also creating the gem during the build process.

      1. 0001-Ruby-specific-.gitignore-file.patch
        0.6 kB
        Darryl L. Pierce
      2. 0002-Added-a-new-target-to-copy-rubyRUBY_wrap.cxx-into-th.patch
        2 kB
        Darryl L. Pierce
      3. 0002-Added-a-new-target-to-copy-rubyRUBY_wrap.cxx-into-th.patch
        2 kB
        Darryl L. Pierce
      4. 0003-Added-details-to-the-README.rdoc-file-for-using-the-.patch
        2 kB
        Darryl L. Pierce
      5. 0004-Created-the-Qpid-gem-package.patch
        20 kB
        Darryl L. Pierce
      6. 0004-Created-the-Qpid-gem-package.patch
        21 kB
        Darryl L. Pierce
      7. 0004-Created-the-Qpid-gem-package.patch
        19 kB
        Darryl L. Pierce

        Activity

        Hide
        Darryl L. Pierce added a comment -

        I've updated the 4th patch in this series to allow for specifying the source directory from the commandline.

        The Rakefile can be run from a different directory using the following commandline:

        QPID_RUBY_ROOT=[path to the ruby directory] rake --rakefile [path to the Rakefile] [targets]

        Show
        Darryl L. Pierce added a comment - I've updated the 4th patch in this series to allow for specifying the source directory from the commandline. The Rakefile can be run from a different directory using the following commandline: QPID_RUBY_ROOT= [path to the ruby directory] rake --rakefile [path to the Rakefile] [targets]
        Hide
        Darryl L. Pierce added a comment -

        These two patches supercede the previously uploaded versions.

        The first updates the CMake target to pass to the Rakefile the output directory path. This path will be the binary target path.

        The second patch updates the Rakefile to use the specified path to make sure the GEM file is dropped into the binary build tree.

        Show
        Darryl L. Pierce added a comment - These two patches supercede the previously uploaded versions. The first updates the CMake target to pass to the Rakefile the output directory path. This path will be the binary target path. The second patch updates the Rakefile to use the specified path to make sure the GEM file is dropped into the binary build tree.

          People

          • Assignee:
            Ted Ross
            Reporter:
            Darryl L. Pierce
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development