[Rock-dev] [rock] #131: better error message / behaviour when Ruby libraries are missing their C++ extensions

rock noreply at opendfki.de
Fri Mar 30 15:48:33 CEST 2012


#131: better error message / behaviour when Ruby libraries are missing their C++
extensions
----------------------------+-----------------------------------
 Reporter:  sylvain.joyeux  |      Owner:  rock-dev-mailing-list
     Type:  defect          |     Status:  new
 Priority:  major           |  Milestone:  Rock Release
Component:  base            |   Keywords:
----------------------------+-----------------------------------
 The current issue is that, if one tries to use orocos.rb while the package
 did not get built (for whatever reason), then he gets a LoadError from
 Ruby.

 A better behaviour would be to suggest the autoproj stanza to run.

 Resolution:

  - do a begin ... rescue LoadError in specific places in common Rock
 packages.
  - re-raise the exception with a new message: "package XXX has probably
 not been built yet, or failed to build. Try running autoproj build XXX"

 Impacted packages:

  - gui/vizkit: C++ extension
  - orocos.rb: C++ extension rorocos_ext, typelib
  - orogen: typelib
  - pocolog: typelib
  - roby: C++ extension bgl and marshalling

-- 
Ticket URL: <http://rock.opendfki.de/ticket/131>
rock <http://rock.opendfki.de>
rock: the robot construction kit


More information about the Rock-dev mailing list