-
Notifications
You must be signed in to change notification settings - Fork 1
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
compile issue #1
Comments
The core functionality of WCS lies with communication_node and gazebo_information_plugins. As of June 15th, I've updated WCS with some minor debugging. Now, sample_package no longer depends on communication_node. I compiled sample_package first, and then the whole WCS without any problem. As a better and proper solution, I suggest you to clone WCS again and try to compile only the sample_package. After successful compilation of sample_package you can then try to compile the whole WCS. |
The circular dependency resolved, please check it again. the main reason for putting a sample_package there is if you are going to send some custom data (something that is not already provided in communication_node package) between your robots, find out how to import your custom msg into communication_node.
|
Installing WCS in a fresh workspace gives the following error:
-- +++ processing catkin package: 'communication_node'
-- ==> add_subdirectory(WCS/communication_node)
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
-- Generating .msg files for action communication_node/Registration /home/ubuntu/catkin_ws/src/WCS/communication_node/action/Registration.action
CMake Error at /opt/ros/kinetic/share/genmsg/cmake/genmsg-extras.cmake:263 (message):
Messages depends on unknown pkg: sample_packages (Missing
'find_package(sample_packages)'?)
Call Stack (most recent call first):
WCS/communication_node/CMakeLists.txt:89 (generate_messages)
It seems to me that the communication_node depends on sample_packages, but adding it as a build dependency (package.xml) gives a circular dependency error. On the other side, removing the dependency in the CMakeList.txt of the communication_node gives compilation errors in the that package.
How do I break the cycle properly?
The text was updated successfully, but these errors were encountered: