-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Official method to build ros-kinetic-*realsense*.deb file? #2412
Comments
Hi @byhang Does using the command below to install librealsense SDK 2.50.0 and ROS1 wrapper 2.3.2 together at the same time from Debian packages work for you, please? sudo apt-get install ros-$ROS_DISTRO-realsense2-camera https://github.com/IntelRealSense/realsense-ros#method-1-the-ros-distribution $ROS_DISTRO should enable the installation process to detect that you are using ROS Kinetic and install the appropriate packages. |
@MartyG-RealSense |
@byhang I see that you raised this question a couple of weeks ago at #2394 (comment) and IntelRealSense/librealsense#10624 (comment) It reminded me that ROS Kinetic was made End of Life (EOL) by ROS around the time of wrapper 2.3.0. https://discourse.ros.org/t/preparing-for-final-kinetic-sync/19805 You should still be able to build the 2.3.2 wrapper for Kinetic from source code using the Method 2 instructions of the ROS wrapper. https://github.com/IntelRealSense/realsense-ros#step-2-install-intel-realsense-ros-from-sources |
Thank you very much@MartyG-RealSense, |
The link below indicates that the ' - ' number after the librealsense version number (such as 2.50.0 -1) is a way of distinguishing between old and new versions of the packages. https://github.com/IntelRealSense/librealsense2-release Xenial and Focal are names of Ubuntu versions. Xenial: 16.04 |
get√ |
Dear Intel,
Is there a official method to build ros-kinetic-realsense**.deb** file?
I wanna build kinetic librealsense2-2.50.0 and realsense-2.3.2 from source code in Ubuntu16,but no good idea.
The text was updated successfully, but these errors were encountered: