Failure to deploy HelloWorld example from Component Builder's Manual

Hello list,

To get to the deployer and using the manual chapter 2:
rosrun ocl orocreate-pkg HelloWorld # ... for ROS users
cd HelloWorld
make
{created helloworld.ops. With the comments there is a syntax error, so I removed them}
rosrun ocl deployer-gnulinux -s helloworld.ops -linfo

This results in:
..........
0.136 [ Info ][DeploymentComponent::import] Importing directory HelloWorld ...
0.136 [ Info ][DeploymentComponent::import] Importing directory ./HelloWorld ...
0.136 [ ERROR ][DeploymentComponent::import] Failed to import components, types or plugins from package or directory 'HelloWorld' found in:
0.136 [ ERROR ][DeploymentComponent::import] HelloWorld:HelloWorld/gnulinux:./HelloWorld
Script imported HelloWorld package:
I can create the following component types:
OCL::ConsoleReporting
OCL::FileReporting
OCL::HMIConsoleOutput
OCL::HelloWorld
OCL::LuaComponent
OCL::LuaTLSFComponent
OCL::NetcdfReporting
OCL::TcpReporting
OCL::TimerComponent
OCL::logging::Appender
OCL::logging::FileAppender
OCL::logging::LoggingService
OCL::logging::OstreamAppender
TaskContext
0.138 [ ERROR ][DeploymentComponent::loadComponent] Unable to create Orocos Component 'HelloWorld': unknown component type.
...............

I think I did everything according to the manual. What is going wrong with the import?

Context:
Ubuntu 12.04 64 bit.
ROS groovy added via ubuntu packages
OROCOS installed via http://wiki.ros.org/orocos_toolchain_ros using ubuntu packages
my .bashrc end's in:
source /opt/ros/groovy/setup.bash
source /opt/ros/groovy/stacks/orocos_toolchain/env.sh

Thanks in advance.
Sietse

Failure to deploy HelloWorld example from Component Builder's Ma

hi,

On 10/23/2013 10:48 AM, Sietse Achterop wrote:
> Hello list,
>
> To get to the deployer and using the manual chapter 2:
> rosrun ocl orocreate-pkg HelloWorld # ... for ROS users
> cd HelloWorld
> make
> {created helloworld.ops. With the comments there is a syntax error, so I removed them}
> rosrun ocl deployer-gnulinux -s helloworld.ops -linfo
>
> This results in:
> ..........
> 0.136 [ Info ][DeploymentComponent::import] Importing directory HelloWorld ...
> 0.136 [ Info ][DeploymentComponent::import] Importing directory ./HelloWorld ...
> 0.136 [ ERROR ][DeploymentComponent::import] Failed to import components, types or plugins from package or directory 'HelloWorld' found in:
> 0.136 [ ERROR ][DeploymentComponent::import] HelloWorld:HelloWorld/gnulinux:./HelloWorld
> Script imported HelloWorld package:
> I can create the following component types:
> OCL::ConsoleReporting
> OCL::FileReporting
> OCL::HMIConsoleOutput
> OCL::HelloWorld
> OCL::LuaComponent
> OCL::LuaTLSFComponent
> OCL::NetcdfReporting
> OCL::TcpReporting
> OCL::TimerComponent
> OCL::logging::Appender
> OCL::logging::FileAppender
> OCL::logging::LoggingService
> OCL::logging::OstreamAppender
> TaskContext
> 0.138 [ ERROR ][DeploymentComponent::loadComponent] Unable to create Orocos Component 'HelloWorld': unknown component type.
> ...............
---here there was probably a statement on where orocos is looking for components, probably a too short list---
>
> I think I did everything according to the manual. What is going wrong with the import?
I saw the follow up messages on the mailing list scattered around, but mostly on 'upgrading to 2.7' as way to go,
however we encountered the same problem with a fresh installation in a ROS environment that was easily resolved doing following steps:
*make sure HelloWorld is in the ROS_PACKAGE_PATH, if you use rosws, add it to the workspace
$rosws set Helloworld
(*make sure you sourced orocos_toolchain/env.sh but the tutorial points this out clearly, and the statement below confirms you did it ;) )
*do a rosmake instead of a make in HelloWorld package => it makes a difference, after this orocos was able to find HelloWorld

nick

>
> Context:
> Ubuntu 12.04 64 bit.
> ROS groovy added via ubuntu packages
> OROCOS installed via http://wiki.ros.org/orocos_toolchain_ros using ubuntu packages
> my .bashrc end's in:
> source /opt/ros/groovy/setup.bash
> source /opt/ros/groovy/stacks/orocos_toolchain/env.sh
>
> Thanks in advance.
> Sietse
>

How to get orocos/ros working

Dear list,

Another try failed :(.
Today, after installing ros-hydro via ubuntu packages I did the following:

source /opt/ros/hydro/setup.bash
mkdir -p ~/orocosros/orocos/src
cd ~/orocosros/orocos/src
git clone --recursive git://gitorious.org/orocos-toolchain/orocos_toolchain.git
git clone https://github.com/jhu-lcsr-forks/rtt_ros_integration.git
cd ..
catkin_make_isolated --install -DCORBA_IMPLEMENTATION=OMNIORB
source install_isolated/setup.bash
cd ..
mkdir examples; cd examples
rosrun ocl orocreate-pkg HelloWorld

Error:
[rosrun] Couldn't find executable named orocreate-pkg below /home/p100213/orocosros/orocos/install_isolated/share/ocl
I ad hoc repaired it by creating a symbolic link in directory ~/orocosros/orocos/install_isolated/share/ocl
ln -s /home/p100213/orocosros/orocos/install_isolated/bin
After that the rosrun command works.
Then:

cd HelloWorld
make
rosrun ocl deployer-gnulinux

And in the deployer:
require("print")
import("HelloWorld")

This gives an error:
21.493 [ ERROR ][DeploymentComponent::import] No such package or directory found in search path: HelloWorld. Search path is:
21.493 [ ERROR ][DeploymentComponent::import] /home/p100213/orocosros/orocos/install_isolated/lib/orocos:/opt/ros/hydro/lib/orocos:/usr/local/gurobi510/linux64/lib/orocos:.
21.493 [ ERROR ][DeploymentComponent::import] /home/p100213/orocosros/orocos/install_isolated/lib/orocos/HelloWorld
21.493 [ ERROR ][DeploymentComponent::import] /home/p100213/orocosros/orocos/install_isolated/lib/orocos/gnulinux/HelloWorld
21.493 [ ERROR ][DeploymentComponent::import] /opt/ros/hydro/lib/orocos/HelloWorld
21.493 [ ERROR ][DeploymentComponent::import] /opt/ros/hydro/lib/orocos/gnulinux/HelloWorld
21.493 [ ERROR ][DeploymentComponent::import] /usr/local/gurobi510/linux64/lib/orocos/HelloWorld
21.493 [ ERROR ][DeploymentComponent::import] /usr/local/gurobi510/linux64/lib/orocos/gnulinux/HelloWorld
21.493 [ ERROR ][DeploymentComponent::import] ./HelloWorld
21.493 [ ERROR ][DeploymentComponent::import] ./gnulinux/HelloWorld
= false

(I also tried rosmake instead of make and put the HelloWorld-dir in ROS_PACKAGE_PATH)

What am I doing wrong?

Thanks again,
Sietse

How to get orocos/ros working

Hi Sietse,

We're very close to releasing 2.7 for hydro, so we'll have ubuntu packages
available to fix the first issue you encountered, but thanks for reporting.

For issue 2, see below :

On Fri, Dec 20, 2013 at 10:53 AM, Sietse Achterop <s [dot] achterop [..] ...> wrote:

>
> Dear list,
>
> Another try failed :(.
> Today, after installing ros-hydro via ubuntu packages I did the following:
>
> source /opt/ros/hydro/setup.bash
> mkdir -p ~/orocosros/orocos/src
> cd ~/orocosros/orocos/src
> git clone --recursive git://
> gitorious.org/orocos-toolchain/orocos_toolchain.git
> git clone https://github.com/jhu-lcsr-forks/rtt_ros_integration.git
> cd ..
> catkin_make_isolated --install -DCORBA_IMPLEMENTATION=OMNIORB
> source install_isolated/setup.bash
> cd ..
> mkdir examples; cd examples
> rosrun ocl orocreate-pkg HelloWorld
>
> Error:
> [rosrun] Couldn't find executable named orocreate-pkg below
> /home/p100213/orocosros/orocos/install_isolated/share/ocl
> I ad hoc repaired it by creating a symbolic link in directory
> ~/orocosros/orocos/install_isolated/share/ocl
> ln -s /home/p100213/orocosros/orocos/install_isolated/bin
> After that the rosrun command works.
> Then:
>
> cd HelloWorld
> make
> rosrun ocl deployer-gnulinux
>
> And in the deployer:
> require("print")
> import("HelloWorld")
>
> This gives an error:
> 21.493 [ ERROR ][DeploymentComponent::import] No such package or
> directory found in search path: HelloWorld. Search path is:
> 21.493 [ ERROR ][DeploymentComponent::import]
> /home/p100213/orocosros/orocos/install_isolated/lib/orocos:/opt/ros/hydro/lib/orocos:/usr/local/gurobi510/linux64/lib/orocos:.
> 21.493 [ ERROR ][DeploymentComponent::import]
> /home/p100213/orocosros/orocos/install_isolated/lib/orocos/HelloWorld
> 21.493 [ ERROR ][DeploymentComponent::import]
> /home/p100213/orocosros/orocos/install_isolated/lib/orocos/gnulinux/HelloWorld
> 21.493 [ ERROR ][DeploymentComponent::import]
> /opt/ros/hydro/lib/orocos/HelloWorld
> 21.493 [ ERROR ][DeploymentComponent::import]
> /opt/ros/hydro/lib/orocos/gnulinux/HelloWorld
> 21.493 [ ERROR ][DeploymentComponent::import]
> /usr/local/gurobi510/linux64/lib/orocos/HelloWorld
> 21.493 [ ERROR ][DeploymentComponent::import]
> /usr/local/gurobi510/linux64/lib/orocos/gnulinux/HelloWorld
> 21.493 [ ERROR ][DeploymentComponent::import] ./HelloWorld
> 21.493 [ ERROR ][DeploymentComponent::import] ./gnulinux/HelloWorld
> = false
>
> (I also tried rosmake instead of make and put the HelloWorld-dir in
> ROS_PACKAGE_PATH)
>
> What am I doing wrong?
>

Importing ROS packages is now differently. import("foo") will only locate
"foo" in the RTT_COMPONENT_PATH, so it needs to be installed where the
error message says it should be. So you could extend your
RTT_COMPONENT_PATH environment variable or make install it. If however you
want to import a ROS package *not* in your RTT component path, see
https://github.com/orocos/rtt_ros_integration#dynamically-loading-ros-ba...

which explains to do:

import("rtt_ros")ros.import("my_pkg_name")

Which will however only work if "my_pkg_name" is in your devel space
(ROS_PACKAGE_PATH), so you'd need to source the generated setup.bash such
that rospack find finds it. I didn't figure out myself yet how the exact
workflow is for the helloworld case...

We had to do this separation because it allows the loading code to be much
cleaner and do less guessing what the user tries to do.

I hope this works for you.

Peter

How to get orocos/ros working

On 22-12-13 12:28, Peter Soetens wrote:
> Hi Sietse,
>
> We're very close to releasing 2.7 for hydro, so we'll have ubuntu packages available to fix the first issue you encountered, but thanks for reporting.
> For issue 2, see below :

Hello list,
@Peter: thanks for the response.
I am a little bit further, but still no working Helloworld.
Please find below all steps I take with some comments and questions in between.
I think it ends in not being able to load the HelloWorld component.
Hopefully somebody can shed some light on it.

Thanks in advance,
Sietse

=============================================================================================
source /opt/ros/hydro/setup.bash
mkdir -p ~/orocosros/orocos/src
cd ~/orocosros/orocos/src
git clone --recursive git://gitorious.org/orocos-toolchain/orocos_toolchain.git
(orocos_toolchain/orocos_toolchain/package.xml says this is version 2.7.
Remove line 28 (Utilrb.doc) from orocos_toolchain/utilrb/Rakefile to make it work.
Is not using Utilrb.doc a problem?)
git clone https://github.com/jhu-lcsr-forks/rtt_ros_integration.git
cd ..
catkin_make_isolated --install -DENABLE_CORBA=ON -DCORBA_IMPLEMENTATION=OMNIORB
(without corba making the helloworld program fails, saying it needs corba.
The make says it is not used, but .... )
ln -s ~/orocosros/orocos/install_isolated/bin ~/orocosros/orocos/install_isolated/share/ocl/bin
(this to prevent a known error in rosrun)
source install_isolated/setup.bash
cd ..
mkdir examples; cd examples
export ROS_PACKAGE_PATH=/home/p100213/orocosros/example:$ROS_PACKAGE_PATH
(ROS_PACKAGE_PATH=
/home/p100213/orocosros/example:/home/p100213/orocosros/orocos/install_isolated/share: \
/home/p100213/orocosros/orocos/install_isolated/stacks:/opt/ros/hydro/share:/opt/ros/hydro/stacks
)
(is this correct now?)
rosrun ocl orocreate-pkg HelloWorld
cd HelloWorld
rosmake
rosrun ocl deployer-gnulinux

And in the deployer:
import("rtt_ros")
displayComponentTypes()
This yields:
I can create the following component types:
OCL::ConsoleReporting
OCL::FileReporting
OCL::HMIConsoleOutput
OCL::HelloWorld
OCL::LuaComponent
OCL::LuaTLSFComponent
OCL::NetcdfReporting
OCL::TcpReporting
OCL::TimerComponent
OCL::logging::Appender
OCL::logging::FileAppender
OCL::logging::Log4cxxAppender
OCL::logging::LoggingService
OCL::logging::OstreamAppender
TaskContext
=
ros.import("OCL::HelloWorld")
143.378 [ ERROR ][ROSService::import("OCL::HelloWorld")] Could not find ROS package "OCL::HelloWorld" in ROS_PACKAGE_PATH environment variable.
= false

It still does not see my HelloWorld as far as I can see.
And what is OCL::HelloWorld exactly?
(at some point I had this component working, but it clearly was not my HelloWorld)

How to get orocos/ros working

Hello List,

I am getting a bit desparate with orocos under ros!
I installed on another machine (also Ubuntu 12.04 64-bit), fairly pristine, and installed ros-hydro from deb's.
Then

source /opt/ros/hydro/setup.bash
mkdir -p ~/orocosros/orocos/src
cd ~/orocosros/orocos/src
git clone --recursive git://gitorious.org/orocos-toolchain/orocos_toolchain.git
git clone https://github.com/jhu-lcsr-forks/rtt_ros_integration.git
cd ..
catkin_make_isolated --install -DCORBA_IMPLEMENTATION=OMNIORB
ln -s ~/orocosros/orocos/install_isolated/bin ~/orocosros/orocos/install_isolated/share/ocl/bin
(this to prevent a known error in rosrun, I think)
source install_isolated/setup.bash
cd ..
mkdir examples; cd examples
export ROS_PACKAGE_PATH=/home/p100213/orocosros/example:$ROS_PACKAGE_PATH
(ROS_PACKAGE_PATH=
/home/p100213/orocosros/example:/home/p100213/orocosros/orocos/install_isolated/share: \
/home/p100213/orocosros/orocos/install_isolated/stacks:/opt/ros/hydro/share:/opt/ros/hydro/stacks
)
(is this needed? does this matter?)
rosrun ocl orocreate-pkg HelloWorld
cd HelloWorld
make
(this is what the Component Builders Manual says. Earlier I tried rosmake with some success, but now that fails
immediate with:
No package or stack specified. And current directory 'HelloWorld' is not a package name or stack name.
)

The make ends in:

How to get orocos/ros working

Sieste,

It looks like you're using the new catkin-based rtt_ros_integration with
the beta Orocos 2.7 release, but also treating it like a to rosbuild-based
set-up. Additionally, you're using the JHU fork of rtt_ros_integration
instead of the official one. Sometimes this fork requires additional
unmerged changes in RTT, so you should stick to using the official one.
It's definitely true, though, we need to put some tutorials up for the new
release, now that it's stabilized.

-j
On Jan 21, 2014 10:19 AM, "Sietse Achterop" <s [dot] achterop [..] ...> wrote:

> Hello List,
>
> I am getting a bit desparate with orocos under ros!
> I installed on another machine (also Ubuntu 12.04 64-bit), fairly
> pristine, and installed ros-hydro from deb's.
> Then
>
> source /opt/ros/hydro/setup.bash
> mkdir -p ~/orocosros/orocos/src
> cd ~/orocosros/orocos/src
> git clone --recursive git://
> gitorious.org/orocos-toolchain/orocos_toolchain.git
> git clone https://github.com/jhu-lcsr-forks/rtt_ros_integration.git
> cd ..
> catkin_make_isolated --install -DCORBA_IMPLEMENTATION=OMNIORB
> ln -s ~/orocosros/orocos/install_isolated/bin
> ~/orocosros/orocos/install_isolated/share/ocl/bin
> (this to prevent a known error in rosrun, I think)
> source install_isolated/setup.bash
> cd ..
> mkdir examples; cd examples
> export ROS_PACKAGE_PATH=/home/p100213/orocosros/example:$ROS_PACKAGE_PATH
> (ROS_PACKAGE_PATH=
>
> /home/p100213/orocosros/example:/home/p100213/orocosros/orocos/install_isolated/share:
> \
>
> /home/p100213/orocosros/orocos/install_isolated/stacks:/opt/ros/hydro/share:/opt/ros/hydro/stacks
> )
> (is this needed? does this matter?)
> rosrun ocl orocreate-pkg HelloWorld
> cd HelloWorld
> make
> (this is what the Component Builders Manual says. Earlier I tried
> rosmake with some success, but now that fails
> immediate with:
> No package or stack specified. And current directory
> 'HelloWorld' is not a package name or stack name.
> )
>
> The make ends in:
>

How to get orocos/ros working

Hello List,

to followup on my own question.
I now tried using the official versions of the rtt-ros-integration software.
Please find below the exact history of this try.

506 source /opt/ros/hydro/setup.bash
507 mkdir -p ~/orocosros/orocos/src
508 cd ~/orocosros/orocos/src
509 git clone --recursive git://gitorious.org/orocos-toolchain/orocos_toolchain.git
510 h
511 git clone --recursive http://git.mech.kuleuven.be/robotics/rtt_ros_integration.git
512 git clone --recursive http://git.mech.kuleuven.be/robotics/rtt_ros_comm.git
513 git clone --recursive http://git.mech.kuleuven.be/robotics/rtt_common_msgs.git
514 h
515 git clone --recursive http://git.mech.kuleuven.be/robotics/rtt_geometry.git
516 cd ..
517 catkin_make_isolated --install -DENABLE_CORBA=ON -DCORBA_IMPLEMENTATION=OMNIORB
518 ln -s ~/orocosros/orocos/install_isolated/bin ~/orocosros/orocos/install_isolated/share/ocl/bin
519 source install_isolated/setup.bash
520 cd ../example/
521 ls
522 export ROS_PACKAGE_PATH=/home/p100213/orocosros/example:$ROS_PACKAGE_PATH
523 rosrun ocl orocreate-pkg HelloWorld
524 cd HelloWorld
525 make

This make fails as follows:

p100213@fwn-nb4-16-202:~/orocosros/example/HelloWorld$ make
mkdir -p bin
cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=/opt/ros/hydro/share/ros/core/rosbuild/rostoolchain.cmake ..

How to get orocos/ros working

On 21-01-14 17:03, Jonathan Bohren wrote:
> Sieste,
>
> It looks like you're using the new catkin-based rtt_ros_integration with the beta Orocos 2.7 release,

Dear Jonathan,

thanks.
Yes, i seem to be using that. But I assumed that the git-clone command that I used would give me the current "stable" verstion of the toolchain.

but also treating it like a to rosbuild-based set-up.

I assume that you main that I am aiming at getting it to work under ros? Yes I do. Orocos without Ros is working fine by the way.
I don't understand the word "but" here. Does that mean that Orocos 2.7 does not yet work properly with ROS?

> Additionally, you're using the JHU fork of rtt_ros_integration instead of the official one.

I didn't realise that I did.
The "official" version that I could find is a version for groovy. I mean that when using http://wiki.ros.org/orocos_toolchain_ros
there is no documentation when selecting hydro. There is for groovy however.
So which version should I use with hydro?

The question that I actually have is, how would an installation script (like the one below) look to create a working ros/orocos setup that
works with ros-hydro?
As far as a tutorial is concerned, a concrete script like below is all that is needed, as far as I am concerned.

Sietse

> source /opt/ros/hydro/setup.bash
> mkdir -p ~/orocosros/orocos/src
> cd ~/orocosros/orocos/src
> git clone --recursive git://gitorious.org/orocos-toolchain/orocos_toolchain.git <http://gitorious.org/orocos-toolchain/orocos_toolchain.git>
> git clone https://github.com/jhu-lcsr-forks/rtt_ros_integration.git
> cd ..
> catkin_make_isolated --install -DCORBA_IMPLEMENTATION=OMNIORB
> ln -s ~/orocosros/orocos/install_isolated/bin ~/orocosros/orocos/install_isolated/share/ocl/bin
> (this to prevent a known error in rosrun, I think)
> source install_isolated/setup.bash
> cd ..
> mkdir examples; cd examples
> export ROS_PACKAGE_PATH=/home/p100213/orocosros/example:$ROS_PACKAGE_PATH
> (ROS_PACKAGE_PATH=
> /home/p100213/orocosros/example:/home/p100213/orocosros/orocos/install_isolated/share: \
> /home/p100213/orocosros/orocos/install_isolated/stacks:/opt/ros/hydro/share:/opt/ros/hydro/stacks
> )
> (is this needed? does this matter?)
> rosrun ocl orocreate-pkg HelloWorld
> cd HelloWorld
> make
> rosrun ocl deployer-gnulinux

Ruben Smits's picture

How to get orocos/ros working

On Tue, Jan 21, 2014 at 4:19 PM, Sietse Achterop <s [dot] achterop [..] ...> wrote:

> Hello List,
>
> I am getting a bit desparate with orocos under ros!
> I installed on another machine (also Ubuntu 12.04 64-bit), fairly
> pristine, and installed ros-hydro from deb's.
> Then
>
> source /opt/ros/hydro/setup.bash
> mkdir -p ~/orocosros/orocos/src
> cd ~/orocosros/orocos/src
> git clone --recursive git://
> gitorious.org/orocos-toolchain/orocos_toolchain.git
> git clone https://github.com/jhu-lcsr-forks/rtt_ros_integration.git
> cd ..
> catkin_make_isolated --install -DCORBA_IMPLEMENTATION=OMNIORB
> ln -s ~/orocosros/orocos/install_isolated/bin
> ~/orocosros/orocos/install_isolated/share/ocl/bin
> (this to prevent a known error in rosrun, I think)
> source install_isolated/setup.bash
> cd ..
> mkdir examples; cd examples
> export ROS_PACKAGE_PATH=/home/p100213/orocosros/example:$ROS_PACKAGE_PATH
> (ROS_PACKAGE_PATH=
>
> /home/p100213/orocosros/example:/home/p100213/orocosros/orocos/install_isolated/share:
> \
>
> /home/p100213/orocosros/orocos/install_isolated/stacks:/opt/ros/hydro/share:/opt/ros/hydro/stacks
> )
> (is this needed? does this matter?)
> rosrun ocl orocreate-pkg HelloWorld
> cd HelloWorld
> make
> (this is what the Component Builders Manual says. Earlier I tried
> rosmake with some success, but now that fails
> immediate with:
> No package or stack specified. And current directory
> 'HelloWorld' is not a package name or stack name.
> )
>
> The make ends in:
>

How to get orocos/ros working (solved)

Hello List,
thanks Ruben and Jonothan, for your help.
I now have it working with the official rtt_ros_integration package.

One minor point about the documentation of this package:
In the "Building OROCOS From Source" there is mentioning of
source install/setup.sh
that should be
source install_isolated/setup.sh

Thanks again.
Sietse

How to get orocos/ros working

On 21-01-14 16:56, Ruben Smits wrote:

>
> -- [UseOrocos] Generating typekit for HelloWorld ...
> Cannot require 'typelib'
>
> Can you post the contents of the RUBYLIB environment variable after sourcing sourcing the install_isolated/setup.bash?
>

Hello Ruben,
I tried the install with the official (?) rtt-ros-integration software, see
my other response just before this one.
There is NO RUBYLIB environment variable when I open a new terminal window and do:

source /opt/ros/hydro/setup.bash
source ~/orocosros/orocos/install_isolated/setup.bash
echo $RUBYLIB

Nothing here......

Sietse

How to get orocos/ros working

Al 22/12/13 12:28, En/na Peter Soetens ha escrit:
> Hi Sietse,
>
> We're very close to releasing 2.7 for hydro, so we'll have ubuntu packages
> available to fix the first issue you encountered, but thanks for reporting.

I don't understand this. Tully Foote send a message on December 18th
with the subject "New Packages in Groovy and Hydro". In the body, you
could see:

----------------------------
...
> Updated Packages [110]:
...
> - ros-hydro-rtt: 2.7.0-1 -> 2.7.0-2
...
> - ros-hydro-ocl: 2.7.0-0 -> 2.7.0-1
...

with your respective credits:

.....
> Thanks to all ROS maintainers who make packages available to the ROS
> community. The above list of packages was made possible by the work
> of the following maintainers:
...
> - OCL Development Team
...
> - RTT Developers
> - Ruben Smits

after read that, I thought that it was strange that there wasn't mail in
the orocos list, or whatever. So, please could you clarify if we have or
not 2.7 of orocos toolchain?

Thanks,

and Merry Xmas and happy new year,

Leo

Ruben Smits's picture

How to get orocos/ros working

Hi Leo,

On Mon, Dec 23, 2013 at 1:23 AM, Leopold Palomo-Avellaneda
<leopold [dot] palomo [..] ...> wrote:
> Al 22/12/13 12:28, En/na Peter Soetens ha escrit:
>> Hi Sietse,
>>
>> We're very close to releasing 2.7 for hydro, so we'll have ubuntu packages
>> available to fix the first issue you encountered, but thanks for reporting.
>
>
> I don't understand this. Tully Foote send a message on December 18th
> with the subject "New Packages in Groovy and Hydro". In the body, you
> could see:
>
> ----------------------------
> ...
>> Updated Packages [110]:
> ...
>> - ros-hydro-rtt: 2.7.0-1 -> 2.7.0-2
> ...
>> - ros-hydro-ocl: 2.7.0-0 -> 2.7.0-1
> ...
>
> with your respective credits:
>
> .....
>> Thanks to all ROS maintainers who make packages available to the ROS
>> community. The above list of packages was made possible by the work
>> of the following maintainers:
> ...
>> - OCL Development Team
> ...
>> - RTT Developers
>> - Ruben Smits
>
>
> after read that, I thought that it was strange that there wasn't mail in
> the orocos list, or whatever. So, please could you clarify if we have or
> not 2.7 of orocos toolchain?
>

We are still working on release candidates: see the tags in the
various git repositories. The idea was to release them as v2.7.0-rcx
using bloom for ROS, but apparently after releasing the first rc,
bloom can only handle major.minor.patch releases in its debian
versioning scheme.

So we currently are still on 2.7.0-rc but are close to 2.7.0, the
latest changes were primarily on the build system to support
rosbuild/catkin/autoproj/plain cmake. We actually plan to release this
week.

Ruben

> Thanks,
>
> and Merry Xmas and happy new year,
>
>
> Leo
>
>
>
> --
> --
> Leopold Palomo-Avellaneda <leopold [dot] palomo [..] ...>
> Institut d'Organització i Control de Sistemes Industrials -IOC-
> Universitat Politècnica de Catalunya -UPC-
>
> Institute of Industrial and Control Engineering
> Technical University of Catalonia
> Avda. Diagonal 647, pl. 11
> 08028 BARCELONA (Spain)
>
> Tel. +34-934017163
> Fax. +34-934016605
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

How to get orocos/ros working

Al 23/12/13 09:01, En/na Ruben Smits ha escrit:
> Hi Leo,
>
> On Mon, Dec 23, 2013 at 1:23 AM, Leopold Palomo-Avellaneda
> <leopold [dot] palomo [..] ...> wrote:
>> Al 22/12/13 12:28, En/na Peter Soetens ha escrit:
>>> Hi Sietse,
>>>
>>> We're very close to releasing 2.7 for hydro, so we'll have ubuntu packages
>>> available to fix the first issue you encountered, but thanks for reporting.
>>
>>
>> I don't understand this. Tully Foote send a message on December 18th
>> with the subject "New Packages in Groovy and Hydro". In the body, you
>> could see:
>>
>> ----------------------------
>> ...
>>> Updated Packages [110]:
>> ...
>>> - ros-hydro-rtt: 2.7.0-1 -> 2.7.0-2
>> ...
>>> - ros-hydro-ocl: 2.7.0-0 -> 2.7.0-1
>> ...
>>
>> with your respective credits:
>>
>> .....
>>> Thanks to all ROS maintainers who make packages available to the ROS
>>> community. The above list of packages was made possible by the work
>>> of the following maintainers:
>> ...
>>> - OCL Development Team
>> ...
>>> - RTT Developers
>>> - Ruben Smits
>>
>>
>> after read that, I thought that it was strange that there wasn't mail in
>> the orocos list, or whatever. So, please could you clarify if we have or
>> not 2.7 of orocos toolchain?
>>
>
> We are still working on release candidates: see the tags in the
> various git repositories. The idea was to release them as v2.7.0-rcx
> using bloom for ROS, but apparently after releasing the first rc,
> bloom can only handle major.minor.patch releases in its debian
> versioning scheme.
>
> So we currently are still on 2.7.0-rc but are close to 2.7.0, the
> latest changes were primarily on the build system to support
> rosbuild/catkin/autoproj/plain cmake. We actually plan to release this
> week.

Ok,

thanks for the clarification. Please, after that, look the log4cpp theme.

Leo

Failure to deploy HelloWorld example from Component Builder's Ma

Dear list,
to add to my previous mail.

I also tried it by installing via rosinstall.
The result is the same, but I noticed the following:
During
rosmake orocos_toolchain rtt_ros_integration rtt_ros_comm rtt_common_msgs rtt_geometry
I see:
.......

Failure to deploy HelloWorld example from Component Builder's Ma

Hello Sietse,

If you're a new user, and you're not already locked into ROS, you
should consider using the orocos toolchain without any of the ROS
stuff. And of course if you don't need real time hardness down to ms
timescales, you should probably not be bothering with orocos and ~just
use ROS.

That may not be terribly helpful, but it may not be obvious to new
users that there is no recommended way of installing orocos; there
were four last I checked:

1. Build the toolchain yourself from the sources (there are maybe 5-10
relevant git repos with pieces of the toolchain, with no parent repo
to integrate the build)
2. Build the toolchain from the linux_quickstart script, which is
installing orocos via the autoproj package manager:

http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux

3. Install from ROS-based packages avalable in some OS's
4. I think Rock may also be able to install orocos, probably also
through autoproj....

The linux quickstart script worked best for me (YMMV).

Cheers,
Andrew

On Thu, Oct 24, 2013 at 1:53 PM, Sietse Achterop <s [dot] achterop [..] ...> wrote:
> Dear list,
> to add to my previous mail.
>
> I also tried it by installing via rosinstall.
> The result is the same, but I noticed the following:
> During
> rosmake orocos_toolchain rtt_ros_integration rtt_ros_comm rtt_common_msgs rtt_geometry
> I see:
> .......
> -- Detecting CXX compiler ABI info - done
> Orocos-RTT found in /home/p100213/ROSWS/orocos/orocos_toolchain/install/lib/cmake/orocos-rtt/orocos-rtt-gnulinux-libraries.cmake
> ROS_ROOT was detected but this package is NOT in your ROS_PACKAGE_PATH. I'm not using any rosbuild-style building.
> [UseOrocos] Building package HelloWorld
> ..........
>
> The ROS_ROOT is /opt/ros/groovy/share/ros
>
> Could this be part of the problem?
> I also did the install on another PC that was freshly installed with the same Ubuntu 12.04, but
> have the same problem there.
>
> Thanks in advance,
> Sietse
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

Ruben Smits's picture

Failure to deploy HelloWorld example from Component Builder's Ma

On Wed, Oct 30, 2013 at 2:55 PM, Andrew Wagner <drewm1980 [..] ...> wrote:
> Hello Sietse,
>
> If you're a new user, and you're not already locked into ROS, you
> should consider using the orocos toolchain without any of the ROS
> stuff. And of course if you don't need real time hardness down to ms
> timescales, you should probably not be bothering with orocos and ~just
> use ROS.
>
> That may not be terribly helpful, but it may not be obvious to new
> users that there is no recommended way of installing orocos; there
> were four last I checked:
>
> 1. Build the toolchain yourself from the sources (there are maybe 5-10
> relevant git repos with pieces of the toolchain, with no parent repo
> to integrate the build)

There is a parent git repos which pulls the most relevant pieces of
the toolchain:

git clone --recursive
http://git.gitorious.org/orocos-toolchain/orocos_toolchain.git -b
toolchain-2.7

This will pull the latest (pre-)released versions of RTT,OCL, log4cpp,
utilmm, utilrb, typelib, rtt_typelib and orogen.

This can be build using plain cmake for each separate package or with
catkin (ROS independent!).

> 2. Build the toolchain from the linux_quickstart script, which is
> installing orocos via the autoproj package manager:
>
> http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux
>
> 3. Install from ROS-based packages avalable in some OS's

packages are available for Ubuntu precise, quantal and raring
(ros-hydro-rtt etc.)

> 4. I think Rock may also be able to install orocos, probably also
> through autoproj....
>
> The linux quickstart script worked best for me (YMMV).
>
> Cheers,
> Andrew
>
> On Thu, Oct 24, 2013 at 1:53 PM, Sietse Achterop <s [dot] achterop [..] ...> wrote:
>> Dear list,
>> to add to my previous mail.
>>
>> I also tried it by installing via rosinstall.

Could you post the exact rosinstall command you used?

>> The result is the same, but I noticed the following:
>> During
>> rosmake orocos_toolchain rtt_ros_integration rtt_ros_comm rtt_common_msgs rtt_geometry
>> I see:
>> .......
>> -- Detecting CXX compiler ABI info - done
>> Orocos-RTT found in /home/p100213/ROSWS/orocos/orocos_toolchain/install/lib/cmake/orocos-rtt/orocos-rtt-gnulinux-libraries.cmake
>> ROS_ROOT was detected but this package is NOT in your ROS_PACKAGE_PATH. I'm not using any rosbuild-style building.
>> [UseOrocos] Building package HelloWorld
>> ..........
>>
>> The ROS_ROOT is /opt/ros/groovy/share/ros
>>
>> Could this be part of the problem?

I would recommend using catkin build instead of rosbuild for the
latest version of the orocos_toolchain.

Ruben

>> I also did the install on another PC that was freshly installed with the same Ubuntu 12.04, but
>> have the same problem there.
>>
>> Thanks in advance,
>> Sietse
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

Failure to deploy HelloWorld example from Component Builder's Ma

On Thu, Oct 31, 2013 at 8:47 AM, Ruben Smits
<ruben [dot] smits [..] ...> wrote:
> There is a parent git repos which pulls the most relevant pieces of
> the toolchain:
>
> git clone --recursive
> http://git.gitorious.org/orocos-toolchain/orocos_toolchain.git -b
> toolchain-2.7
>
> This will pull the latest (pre-)released versions of RTT,OCL, log4cpp,
> utilmm, utilrb, typelib, rtt_typelib and orogen.
>
> This can be build using plain cmake for each separate package or with
> catkin (ROS independent!).

Cool, it works! At least in the sense of making it easier to download
all of the sources in a standard way. Is there some deficiency in
CMake that makes it undesirable to fully integrate the toolchain
build? I remember CMake ~sorta supported nested builds, but it's been
a long time since I looked into it.

Ruben Smits's picture

Failure to deploy HelloWorld example from Component Builder's Ma

Hi Andrew:

On Tue, Nov 5, 2013 at 12:40 PM, Andrew Wagner <drewm1980 [..] ...> wrote:
> On Thu, Oct 31, 2013 at 8:47 AM, Ruben Smits
> <ruben [dot] smits [..] ...> wrote:
>> There is a parent git repos which pulls the most relevant pieces of
>> the toolchain:
>>
>> git clone --recursive
>> http://git.gitorious.org/orocos-toolchain/orocos_toolchain.git -b
>> toolchain-2.7
>>
>> This will pull the latest (pre-)released versions of RTT,OCL, log4cpp,
>> utilmm, utilrb, typelib, rtt_typelib and orogen.
>>
>> This can be build using plain cmake for each separate package or with
>> catkin (ROS independent!).
>
> Cool, it works! At least in the sense of making it easier to download
> all of the sources in a standard way. Is there some deficiency in
> CMake that makes it undesirable to fully integrate the toolchain
> build? I remember CMake ~sorta supported nested builds, but it's been
> a long time since I looked into it.

This is not supported yet for the toolchain itself, but it should be
for all oro-created packages. It has been tested with catkin_make
which does a nested build and adds dependency resolution.

Ruben

Failure to deploy HelloWorld example from Component Builder's Ma

On 31-10-13 08:47, Ruben Smits wrote:
>
> There is a parent git repos which pulls the most relevant pieces of the toolchain:
>
> git clone --recursive http://git.gitorious.org/orocos-toolchain/orocos_toolchain.git -b toolchain-2.7
>
> This will pull the latest (pre-)released versions of RTT,OCL, log4cpp, utilmm, utilrb, typelib, rtt_typelib and orogen.
> This can be build using plain cmake for each separate package or with catkin (ROS independent!).

Hello Ruben,

I still am struggling with this cmake/catkin stuff.
I create a catkin workspace, download the toolchain via git in the scr-dir and call catkin_make.
But I get the following error.
See below the exact commands and the result.
Wat am I doing wrong?

The commands:
source /opt/ros/hydro/setup.bash
mkdir -p catkin_ws/src
cd catkin_ws
catkin_make
source devel/setup.bash
cd src
git clone --recursive http://git.gitorious.org/orocos-toolchain/orocos_toolchain.git -b toolchain-2.7
cd ..
catkin_make

we then get:

Base path: /home/p100213/catkin_ws
Source space: /home/p100213/catkin_ws/src
Build space: /home/p100213/catkin_ws/build
Devel space: /home/p100213/catkin_ws/devel
Install space: /home/p100213/catkin_ws/install
####
#### Running command: "make cmake_check_build_system" in "/home/p100213/catkin_ws/build"
####

Failure to deploy HelloWorld example from Component Builder's Ma

Please forget my last message,
I found the command:
catkin_make_isolated --install

and it's building now.
Sietse

Failure to deploy HelloWorld example from Component Builder's Ma

Hello,

Thanks Andrew and Ruben for the responses.

>>> I also tried it by installing via rosinstall.
>
> Could you post the exact rosinstall command you used?
>

I just followed the second option from:
http://wiki.ros.org/orocos_toolchain_ros

(apart from the line: rosws init . /opt/ros/fuerte
i changed fuerte to groovy)

But after that I thought that I better first concentrate on OROCOS only.

For that I used the quick start from
http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux

This gave the error
INFO: cannot load the Hoe gem. Distribution is disabled
INFO: error message is: no such file to load -- hoe
rake aborted!
undefined method `<<' for LL():Rake::Scope::EmptyScope
./lib/utilrb/doc/rake.rb:40:in `doc'
/home/p100213/orocos/orocos-toolchain/utilrb/Rakefile:27

I commented out line 27 of utilrb/Rakefile as in:
#Utilrb.doc

Now everything seems to work perfectly. I tried some hello world examples,
and am beginning to understand the workings of OROCOS!

But what is removed by removing Utilrb.doc, and how can it be repaired?
(I now will try toolchain-2.7 from git)

Regards.
Sietse