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
Dear Sacha,
Once the init.rb has been updated, what has to be done ? I have launched a
rebuild, but without success.
Pierre
- Original Message -
From: Sascha Arnold sascha.arn...@dfki.de
To: rock-dev@dfki.de
Sent: Wednesday, 26 August, 2015 3:56:32 PM
Subject: Re: [Rock-dev] Fwd: Fwd:
- 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
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
Hi Steffen.
Finally have had the opportunity to test - and it works the way you
described it.
Thanks a lot for solving that riddle for me !
Am 20.08.2015 um 13:09 schrieb Steffen Planthaber:
Hi,
It seems like the curl parser is now checking the content before
sending. Actually the syntax
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
Hi,
I'm not familiar with the rock ros integration.
But my guess is that tools/rtt_transports/ros and tools/orogen_ros are
obsolete, since they are part of orogen and orocos.rb now.
Maybe it is enough now to activate the support by adding
Autoproj.env_set 'USE_ROS', true
to the init.rb
There
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