Jsk_rviz_plugins lost after building rviz from source
krtt opened this issue · 2 comments
I use Ubuntu 20.04 and ROS Noetic. I built rviz from source (with newer version of Ogre) and after that the jsk_rviz_plugin/Plotter2D does not load any more. I checked that my new rviz workspace is sourced and everything else regarding rviz seems to work fine. I checked with rospack find and the jsk_rviz_plugins is not found any more. How can it get lost and how can I avoid it happen?
@krtt I have confirmed that Plotter2D works fine on the current master branch.
If you haven't found jsk_rviz_plugins with rospack, the package would not be built correctly, but we don't know much more than that without logs or other information.
Please paste the build log by pasting catkin build jsk_rviz_plugins -v or cd build/jsk_rviz_plugins && make 's output.
Multiple answers that I have found out:
- Yes, jsk_rviz_plugins and Plotter2D works in default ROS installation (we have used it for a long time). But not if rviz is built from source with newer Ogre (we need newer Ogre because rviz crashes on Publish Point functionality with Ogre 1.9.0).
- If rviz is built with Ogre 1.12 (my example case), then jsk_rviz_plugins (and a lot of other packages) are removed because Ogre 1.9.0 cannot coexist with 1.12 and gets removed. Jsk_rviz_plugins seems to be also dependent on Ogre 1.9.0 and so gets removed too (among others). This answers my question 'how' it gets lost. I thought it was a bug but it's not. It's just a dependency that was not visible to me at first and that is so old (Ogre 1.9.0) that it is difficult to find a workaround. Now the problem is how to avoid the plugin getting removed.
Do I understand correctly that the only way is to figure out how to build jsk_rviz_plugins with newer Ogre?
One failed attempt here where I tried to build rviz and jsk_rviz_plugin from source with rviz being built with Ogre 1.12: cannot_build_jsk_rviz_plugins_with_rviz_with_ogre1.12.txt