Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross-compilation rtt_ros_integration on Raspberry Pi 3 #120

Open
MatheusPinto opened this issue Mar 18, 2019 · 1 comment
Open

Cross-compilation rtt_ros_integration on Raspberry Pi 3 #120

MatheusPinto opened this issue Mar 18, 2019 · 1 comment

Comments

@MatheusPinto
Copy link

Hello,

For about 1 month, I am trying to make a cross-compile of a application from rtt_ros_integration on Ubuntu 16.04 to a Raspberry Pi 3 running Ubuntu Mate Xenial. After several trial and error, I finally achieve to create the file that can be executed on Raspberry Pi 3. The code was created with the base from here: #118. However, when the program go to rtt_ros::import("rtt_std_msgs"), the follow error is launched:

0.660 [ ERROR  ][ROSService::import("rtt_std_msgs")] No paths in the ROS_PACKAGE_PATH environment variable! Could not load ROS package "rtt_std_msgs"
Segmentation fault

The "rtt_std_msgs" package is not founded for application. knowing this, I'm sure I'll have been able to do the cross compilation of rtt_ros_integration. Could any developer help me?

@MatheusPinto MatheusPinto changed the title Cross-compilation rtt_ros_integration o Raspberry Pi 3 Cross-compilation rtt_ros_integration on Raspberry Pi 3 Mar 18, 2019
@mvukov
Copy link

mvukov commented May 13, 2019

There is a simple fact, but not immediately obvious. When you compile orocos and friends, you must copy the install space to the board to exactly the same path (at least I do that, and that was the case about ~2 years ago). So, if your install space path on the host is:

/home/user/my_ws/install

then you have to copy the install space to that exact path on a rpi3 -- this is related to how OROCOS component/typekit loader works.

Once you copy the install space, do

source /home/user/my_ws/install/setup.sh

and you are ready to go: run the deployer and execute your scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants