-
Notifications
You must be signed in to change notification settings - Fork 162
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
Compilation for Ubuntu 18.04.4 LTS #93
Comments
@pryre Thanks for opening this issue. Seems like the link time optimizer is doing something incorrectly. Can you make a PR with the change that made it work? Thanks! |
Hey @pryre! I've got ROS Melodic running on my RPI 4 (under Raspbian Buster). I managed to have a copy of the raspicam_node running, however when I run the tutorial.launch and afterwards I run Here is the erros message I get:
|
@pryre @guillermoherreraf how did you manage to get it running under 18.04.4? I cannot build cause libraspberrypi0 is missing. Any hint welcome, I'm stuck. |
I am having problems building this from src on Ubuntu Server 16.04 as well as it is unable to locate libraspberrypi-dev or libraspberrypi0. Also looking for any suggestions? robo1@robuntudev:~/catkin_ws$ rosdep install --from-paths src --ignore-src --rosdistro=kinetic -y |
@bltDefender I changed to the usb_cam node. I could not manage to make the raspicam_node work with my system configuration. http://wiki.ros.org/usb_cam |
Not sure on the priority, but I have managed to get a running copy of raspicam_node on the new Ubuntu 18.04.4 LTS release using ROS melodic. Everything seems to be working as expected (except I haven't actually opened an image_view as I have to run headless for the time being).
The primary problem was a linking issue, similar to this. Compiling in
catkin_ws
gave a binary with the following linking (and some strange compiler warnings):Adding the following line to
CMakeLists.txt
fixed this issue (and removed the warnings):Resulting binary was is linked as:
The actual issue that is referenced above is a bit complicated for me to dive into at the moment, but this fix seems to work temporarily at least. Hopefully it helps anyone passing by.
Additional info: I would recommend reading this page for getting the native Pi packages set up. I also had to add the following to
/boot/firmware/config.txt
to get the Pi detected (adding it tousercfg.txt
did no seem to work for both RPi2 and RPi4):The result was as detected shows:
The text was updated successfully, but these errors were encountered: