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
libgflags link error #7
Comments
it seems well now after install libgflags. but it has “Segmentation fault” when parse param with "OPTION_CLAUSE" function. |
Hi, Do you have an error associated with the Segmentation Fault (perhaps before) ? I will need a bit more to be able to help you, Best Regards, |
thanks, |
OPTION_CLAUSE is a MACRO, so you can look at the code it generates to see if there is any problem. So i understand that it fails at "OPTION_CLAUSE(icp_node, icp_options, threshold_voxel_occupancy, int);" Can you:
|
ok, |
and i'm confused with "kitti_raw_transform_trajectory_frame()" function: thanks a lot. |
T_lidar2came * T_lidar2world * inv(T_lidar2came) |
Hi, |
I have fixed it by replace "find_package(glfw3 REQUIRED CONFIG PATHS ${GLFW_DIR})" with "find_package(glfw3 3.3 REQUIRED CONFIG PATHS ${GLFW_DIR})" in external.cmake file. |
So it didn't work with gcc8 ? That is strange as I had no problem with gcc-7.5. I will investigate. Your latest problem is probably due to conflicting glfw installed on your system and cmake-build-Release/external The "proper way" to fix it would be to add NO_DEFAULT_PATH to the cmake command find_package(glfw3 REQUIRED CONFIG PATHS ${GLFW_DIR} NO_DEFAULT_PATH) |
|
And by the way, how to change pcd file to ply used in ct-icp. I found the "writeFile()" function in "PlyFile.h" ,but I cann't use it well. thanks. |
Hi,thanks for your work
when I run "./slam -c robust_high_frequency_config.yaml" ,the output is "error while loading shared libraries: libgflags.so.2.2: cannot open shared object file: No such file or directory". I have install gflag in “usr/local/”. And I can't find where link gflags in cmakelists.txt.
hope for your reply,thanks a lot.
The text was updated successfully, but these errors were encountered: