Lib Qt5::Gui references libEGL.so but this file does not exist
Hi, I have followed the steps to install ROS1 under Ubuntu 16.04. Then, I installed some libraries for my robot. When I executed catkin_make in the last step, the titled error showed up. Can you tell me how to fix this please? Thanks
Here is the commands I used:
cd Downloads/
ls
chmod +x NVIDIA-Linux-x86_64-440.82.run
sudo ./NVIDIA-Linux-x86_64-440.82.run --no-x-check
sudo reboot
sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list'
sudo apt-key adv --keyserver 'hkp://keyserver.ubuntu.com:80' --recv-key C1CF6E31E6BADE8868B172B4F42ED6FBAB17C654
sudo apt-get update
sudo apt-get install ros-kinetic-desktop-full
sudo apt install python-rosdep python-rosinstall python-rosinstall-generator python-wstool build-essential
sudo sudo apt install python-rosdep
sudo rosdep init
rosdep update
echo "source /opt/ros/kinetic/setup.bash" >> ~/.bashrc
source ~/.bashrc
env | grep ROS
vi .bashrc
mkdir -p ~/catkin_ws/src
cd ~/catkin_ws/
catkin_make
cd devel
ls
cd ..
source devel/setup.bash
echo $ROS_PACKAGE_PATH
/home/youruser/catkin_ws/src:/opt/ros/kinetic/share
echo $ROS_PACKAGE_PATH /home/youruser/catkin_ws/src:/opt/ros/kinetic/share
cd ~
sudo apt-get install ros-kinetic-ros-controllers ros-kinetic-gazebo* ros-kinetic-moveit* ros-kinetic-industrial-core
cd ~/catkin_ws/src/
git clone https://github.com/ROBOTIS-GIT/DynamixelSDK.git
git clone https://github.com/ROBOTIS-GIT/dynamixel-workbench.git
git clone https://github.com/ROBOTIS-GIT/dynamixel-workbench-msgs.git
git clone https://github.com/ROBOTIS-GIT/open_manipulator.git
git clone https://github.com/ROBOTIS-GIT/open_manipulator_msgs.git
git clone https://github.com/ROBOTIS-GIT/open_manipulator_simulations.git
git clone https://github.com/ROBOTIS-GIT/robotis_manipulator.git
cd ~/catkin_ws && catkin_make
Output of catkin_make:
user@ubuntu:~/catkin_ws$ catkin_make
Base path: /home/user/catkin_ws
Source space: /home/user/catkin_ws/src
Build space: /home/user/catkin_ws/build
Devel space: /home/user/catkin_ws/devel
Install space: /home/user/catkin_ws/install
####
#### Running command: "make cmake_check_build_system" in "/home/user/catkin_ws/build"
####
-- Using CATKIN_DEVEL_PREFIX: /home/user/catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /home/user/catkin_ws/devel;/opt/ros/kinetic
-- This workspace overlays: /home/user/catkin_ws/devel;/opt/ros/kinetic
-- Found PythonInterp: /usr/bin/python2 (found suitable version "2.7.12", minimum required is "2")
-- Using PYTHON_EXECUTABLE: /usr/bin/python2
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/user/catkin_ws/build/test_results
-- Found gtest sources under '/usr/src/gmock': gtests will be built
-- Found gmock sources under '/usr/src/gmock': gmock will be built
-- Found PythonInterp: /usr/bin/python2 (found version "2.7.12")
-- Using Python nosetests: /usr/bin/nosetests-2.7
-- catkin 0.7.20
-- BUILD_SHARED_LIBS is on
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~ traversing 16 packages in topological order:
-- ~~ - dynamixel_workbench (metapackage)
-- ~~ - open_manipulator (metapackage)
-- ~~ - open_manipulator_simulations (metapackage)
-- ~~ - dynamixel_workbench_msgs
-- ~~ - open_manipulator_msgs
-- ~~ - dynamixel_sdk
-- ~~ - dynamixel_workbench_toolbox
-- ~~ - robotis_manipulator
-- ~~ - open_manipulator_libs
-- ~~ - dynamixel_workbench_controllers
-- ~~ - dynamixel_workbench_operators
-- ~~ - open_manipulator_control_gui
-- ~~ - open_manipulator_controller
-- ~~ - open_manipulator_teleop
-- ~~ - open_manipulator_description
-- ~~ - open_manipulator_gazebo
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin metapackage: 'dynamixel_workbench'
-- ==> add_subdirectory(dynamixel-workbench/dynamixel_workbench)
-- +++ processing catkin metapackage: 'open_manipulator'
-- ==> add_subdirectory(open_manipulator/open_manipulator)
-- +++ processing catkin metapackage: 'open_manipulator_simulations'
-- ==> add_subdirectory(open_manipulator_simulations/open_manipulator_simulations)
-- +++ processing catkin package: 'dynamixel_workbench_msgs'
-- ==> add_subdirectory(dynamixel-workbench-msgs/dynamixel_workbench_msgs)
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
-- dynamixel_workbench_msgs: 18 messages, 2 services
-- +++ processing catkin package: 'open_manipulator_msgs'
-- ==> add_subdirectory(open_manipulator_msgs)
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
-- open_manipulator_msgs: 3 messages, 6 services
-- +++ processing catkin ...
Seeing as this is a build issue with
open_manipulator_control_gui: have you asked the developers/maintainers of that package?Edit: it seems like you did: ROBOTIS-GIT/open_manipulator#159. Could I ask you to please not cross-post like this?
As we just had a bit of a holiday, I would suggest you give ROBOTIS a bit more time to respond instead of posting duplicates here.
Thanks. I have been trying to get this OpenManipulator packages installed for over a month already. If you check that forum, you can see that some of my questions are not answered for almost a month or not get any answer. I posted here to see if other ROS users could help as it seems that some users of other non-Robotis packages also had this issue. Google it but still cannot find a solution.
If you've bought one of their products, I would really advise you to contact their customer support.
Although I can imagine they may be either a bit busy -- due to Corona -- or even incapable of responding to you -- again, due to Corona -- as a customer the vendor would seem to be the first point of inquiry.
They just keep me waiting week after week all the time. I am still waiting for them to resolve various issues both ROS-wise and hardware-wise. Basically, I cannot get pass the setup stage. Now they told me that the return period has passed and I cannot get a refund or a new replacement. For motors that came defective, repairing is the only option.