Dear Steffen, This last step makes it working. I have still an issue with rock-display that crashes after this procedure (not before), although it shows the ROS connection....
So, the current working procedure is (waiting maybe for a easier solution): 1. install stable branch 2. paste tools/orogen_ros and tools/rtt_transports/ros 3. Add them in the manifest 4. add Autobuild::Orogen.transports << 'ros' in init.rb 5. Add file ros.osdeps in autoproj folder (https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps) 5. amake rebuild Thank you, Pierre ----- Original Message ----- From: "Steffen Planthaber" <steffen.plantha...@dfki.de> To: "Pierre Letier" <pierre.let...@spaceapplications.com> Cc: "rock-dev" <rock-dev@dfki.de> Sent: Wednesday, 26 August, 2015 3:28:49 PM Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious Hi, Just guessing but it could be, that a autoproj rebuild is nessecary to actually build the new transport for all the packages, but i'm not sure. Best, Steffen Am 26.08.2015 um 15:23 schrieb Pierre Letier: > Hi, > > I continued with my trials and here is the status: > > - on a first install (one I have tested several things), I succeeded to > publish on ROS > - on a new install (stable branch), I have still a problem. Here is what I > have done: > > 1. install stable branch > 2. paste tools/orogen_ros and tools/rtt_transports/ros > 3. Add them in the manifest > 4. add Autobuild::Orogen.transports << 'ros' in init.rb > 5. amake > > I receive then the following error when starting a simple component that > publishes on ROS (a base/Pose type): > : 'publish_on_ros': uninitialized constant Orocos::TRANSPORT_ROS > > 6. acd orocos.rb > 7. rake clean > 8. rake > > I receive then the following error when starting a simple component that > publishes on ROS (a base/Pose type): > 'Caught std::exceptio. what(): Requesting to start as ROS node, but the > support for 'ros' transport is not available. Recompile with 'ros' transport > option! > > 9. aup > 10. amake > > same error as after 8. > > I also tested rock-display, that shows now the Orocos::ROS:NameService, but > crahses after 1 sec, with the following error: Wrong size, Was 1513, should > be 284 (RuntimeError) ?? Not sure it is related to the problem above > > For the ROS bridge, I guess I am missing a step. Do you have any idea ? > > Best, > > Pierre > > > > ----- Original Message ----- > From: "Steffen Planthaber" <steffen.plantha...@dfki.de> > To: "Pierre Letier" <pierre.let...@spaceapplications.com> > Cc: "rock-dev" <rock-dev@dfki.de> > Sent: Wednesday, 26 August, 2015 11:50:54 AM > Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious > > Hi, > > can you send me the two packages (zipped or upload them on github)? > > So we could re-establish rock-ros on github. > > tools/rtt_transports/ros > and > tools/orogen_ros > > Where I guess the second is not needed anymore. > > Best, Steffen > > > Am 26.08.2015 um 11:41 schrieb Pierre Letier: >> Hi, >> >> My packages come from a previous installation I have done when gitorious was >> still accessible. I also found the gitorious package in the ".remote" >> folder. Is it possible to avoid to access gitorious and launch the >> "standard" installation. With the current process, i never stipulate what >> flavor of ROS I am using and I don't know if it can have an influence. >> >> I will test your solution and let you know (i am resinstalling a proper >> system, after my trials...) >> >> Pierre >> >> ----- Original Message ----- >> From: "Steffen Planthaber" <steffen.plantha...@dfki.de> >> To: rock-dev@dfki.de >> Sent: Wednesday, 26 August, 2015 11:18:07 AM >> Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious >> >> Hi, >> >> rock.ros is the package_set I created to integrate catkin builds into >> autoproj (as far a i remember). >> >> There I have a ros.osdeps file which tells autoproj to ignore ros >> dependencies (assume it is installed): >> >> here is the raw link, you can just drop it into your buildconf(autoproj >> folder): >> >> https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps >> >> >> Two packages are required for the ros bridge: >> >> - tools/rtt_transports/ros: >> gitorious: orocos-communication/ros-transport >> branch: $ROCK_FLAVOR >> - tools/orogen_ros: >> gitorious: rock-ros/orogen_ros >> branch: $ROCK_FLAVOR >> >> But I cannot find any of them on github. >> Can you tell me where your "tools/rtt_transport/ros" comes from? >> >> Best, >> >> Steffen >> >> Am 26.08.2015 um 10:52 schrieb Pierre Letier: >>> >>> >>> ----- Forwarded Message ----- >>> From: "Pierre Letier" <pierre.let...@spaceapplications.com> >>> To: "Steffen Planthaber" <steffen.plantha...@dfki.de> >>> Sent: Wednesday, 26 August, 2015 10:52:25 AM >>> Subject: Re: [Rock-dev] Fwd: Re: Access to Gitorious >>> >>> Hello, >>> >>> When following your description, when building, I receive an error as >>> tools/rtt_transport/ros is excluded from the build: it depends on roslib. >>> >>> My ROS is sources. Is this roslib created when compiling rock.ros ? >>> >>> Thank you, >>> >>> Pierre >>> >>> ----- Original Message ----- >>> From: "Steffen Planthaber" <steffen.plantha...@dfki.de> >>> To: "Pierre Letier" <pierre.let...@spaceapplications.com> >>> Cc: rock-dev@dfki.de >>> Sent: Tuesday, 25 August, 2015 4:15:02 PM >>> Subject: Re: [Rock-dev] Fwd: Re: Access to Gitorious >>> >>> Hi, >>> >>> rock-display is unable to display ros types, it can only connect to >>> corba, not roscore. >>> >>> You can use "rostopic list" to see if you can publish your ports to ros >>> port.publish_to_ros >>> >>> To let orogen build the ros types, you need to specify that you want to >>> install the ros transport in your init.rb: >>> >>> Autobuild::Orogen.transports << 'ros' >>> >>> and the package >>> >>> 'tools/rtt_transports/ros' in should be in your manifest >>> >>> I once created a package_set (currently not functional because it is >>> based on gitorious packages) >>> https://github.com/planthaber/ros-package_set which also included catkin >>> into "autoproj build". >>> >>> But I think the contents of the init.rb there may help with your setup. >>> >>> >>> Best, >>> >>> Steffen >>> >>> >>> >>> Am 25.08.2015 um 16:01 schrieb Pierre Letier: >>>> Hi, >>>> >>>> At least the rock-display doesn't show the ROS topics. If it is in the >>>> codebase, is there a need of configuration ? (like during the installation >>>> of the rock-ros bridge). >>>> >>>> Otherwise, I have another installation. Is there a way to take the code >>>> (folder) from this installation ? >>>> >>>> Thank you, >>>> >>>> Best Regards, >>>> >>>> Pierre >>>> >>>> ----- Original Message ----- >>>> From: "Steffen Planthaber" <steffen.plantha...@dfki.de> >>>> To: "Pierre Letier" <pierre.let...@spaceapplications.com> >>>> Cc: rock-dev@dfki.de >>>> Sent: Tuesday, 25 August, 2015 3:42:42 PM >>>> Subject: Re: [Rock-dev] Fwd: Re: Access to Gitorious >>>> >>>> Hi, >>>> >>>> >>>> Am 25.08.2015 um 15:28 schrieb Pierre Letier: >>>>> Thank you Steffen, >>>>> >>>>> Does it mean that we can not have access currently to the last code of >>>>> the ROS-ROCK bridge ? >>>> >>>> No Idea, but the comment says >>>> "orogen_ros functionality is now part of the oroGen codebase", so i >>>> guess it can work out of the box. >>>> >>>> Best, Steffen >>>> >>>> >>>> >>>> >>>>> >>>>> Pierre >>>>> >>>>> ----- Original Message ----- >>>>> From: "Steffen Planthaber" <steffen.plantha...@dfki.de> >>>>> To: rock-dev@dfki.de >>>>> Sent: Tuesday, 25 August, 2015 9:23:03 AM >>>>> Subject: [Rock-dev] Fwd: Re: Access to Gitorious >>>>> >>>>> Accidently replied directly, so here is a forward to the list: >>>>> >>>>> >>>>> -------- Weitergeleitete Nachricht -------- >>>>> Betreff: Re: [Rock-dev] Access to Gitorious >>>>> Datum: Tue, 25 Aug 2015 09:21:49 +0200 >>>>> Von: Steffen Planthaber <steffen.plantha...@dfki.de> >>>>> An: Pierre Letier <pierre.let...@spaceapplications.com> >>>>> >>>>> Hi, >>>>> >>>>> We moved all the rock code to github. >>>>> >>>>> The package_set for the tutorials is located here: >>>>> https://github.com/rock-tutorials, along with the packages. >>>>> >>>>> >>>>> I found an old package belonging to the bridge: >>>>> https://github.com/rock-core/tools-orogen_ros >>>>> >>>>> The description says: >>>>> "DEPRECATED PACKAGE. The orogen_ros functionality is now part of the >>>>> oroGen codebase" >>>>> >>>>> I can't find the previously required package >>>>> "orocos-communication/ros-transport" though. >>>>> >>>>> But perhaps it works directly... >>>>> >>>>> Kind Regards, >>>>> >>>>> Steffen >>>>> >>>>> >>>>> >>>>> Am 25.08.2015 um 07:39 schrieb Pierre Letier: >>>>>> Dear Rock Developers, >>>>>> >>>>>> I tried to reinstall the Rock framework but I have issues to download >>>>>> ROS bridge and tutorials as they are on Gitorious (c.f. manifest file). >>>>>> The Gitorious website is under "migration". How can we have access to >>>>>> these codes ? >>>>>> >>>>>> Thank you, >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> Pierre >>>>>> _______________________________________________ >>>>>> Rock-dev mailing list >>>>>> Rock-dev@dfki.de >>>>>> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > -- Steffen Planthaber Weltraumrobotik Besuchsadresse der Nebengeschäftstelle: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 5 28359 Bremen, Germany Postadresse der Hauptgeschäftsstelle Standort Bremen: DFKI GmbH Robotics Innovation Center Robert-Hooke-Straße 1 28359 Bremen, Germany Tel.: +49 421 178 45-4125 Zentrale: +49 421 178 45-0 Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen) E-Mail: steffen.plantha...@dfki.de Weitere Informationen: http://www.dfki.de/robotik ----------------------------------------------------------------------- Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973 Steuernummer: 19/673/0060/3 ----------------------------------------------------------------------- _______________________________________________ Rock-dev mailing list Rock-dev@dfki.de http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev