ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
OK, so the problem is that g2o could not be found.
Do you have that in your ROS_PACKAGE_PATH when building? (roscd g2o
) should get you there. If you type make, it should start downloaded files and building g2o.
The problem might be that RGBDSLAMs cmake file only finds this via a cmake script and if you cannot install libg2o
on your system that fails.
Adding a <depend package="g2o" />
to RGBDSlam's manifest + removing the find_package(g2o REQUIRED) from CMakeLists.txt should solve this (given g2o builds).
I'm not sure if there is a better cross-distribution way.
2 | No.2 Revision |
OK, so the problem is that g2o could not be found.
Do you have that in your ROS_PACKAGE_PATH when building? (roscd g2o
) should get you there. If you type make, it should start downloaded files and building g2o.
The problem might be that RGBDSLAMs cmake file only finds this via a cmake script and if you cannot install libg2o
on your system that fails.
Adding a <depend package="g2o" />
to RGBDSlam's manifest + removing the find_package(g2o
REQUIRED) REQUIRED) from CMakeLists.txt should solve this (given g2o builds).
I'm not sure if there is a better cross-distribution way.
3 | No.3 Revision |
OK, so the problem is that g2o could not be found.
Do you have that in your ROS_PACKAGE_PATH when building? (roscd g2o
) should get you there. If you type make, it should start downloaded files and building g2o.
The problem might be that RGBDSLAMs cmake file only finds this via a cmake script and if you cannot install libg2o
on your system that fails.
Adding a <depend package="g2o" />
to RGBDSlam's manifest + removing the find_package(g2o REQUIRED)
from CMakeLists.txt should solve this (given g2o builds).
I'm not sure if there is a better cross-distribution way.