-
Notifications
You must be signed in to change notification settings - Fork 186
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
Cannot build newer versions that don't compile CSM #39
Comments
Sorry for the inconvenience. You can now install If you have specific reason to build from source, Please reopen if the above is not sufficient. |
I've made some update. #40 Hope this helps. |
Thanks for the quick response. I'm using ROS Jade, which does work with the version of scan_tools I mention above when build from source. There are no binaries for Jade in the repo. The new instructions do not work with Jade. I when I try to run the wstool line, I get the following error:
If I clone the repo directly into the src directory of my catkin workspace, run the rosdep line (with jade instead of indigo) and then run catkin_make, I get an error that it couldn't find csm. So it seems csm is not automatically compiled in this configuration. I am on Ubuntu 15.04. |
@tlalexander Sorry, #41 is needed too.
Their binary should be available. |
Thanks, compiling from source seems to work now. However, ros-jade-scan-tools is not found in my repo. All the other ros-jade stuff is there. |
Oh, now I see what's going on. I'm working to release the missing packages into Jade. |
Some time around commit d214d70, the function to automatically compile CSM was removed.
Both myself and two other coworkers have tried to compile CSM and link it to this library with no success. I'm not sure what I'm doing wrong, but it was a big pain to try. Ultimately, I switched to the above commit, where CSM is automatically downloaded and compiled, and everything magically worked.
Given that this library depends on CSM, I wonder if it would be worthwhile to put that functionality back, maybe with a command line switch? Alternatively, some suggestions on a known method for compiling and linking with CSM in the documentation would be helpful.
The text was updated successfully, but these errors were encountered: