Skip to content
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

ros melodic/gazebo9 package did not worked #556

Closed
aeudes opened this issue Mar 19, 2019 · 2 comments
Closed

ros melodic/gazebo9 package did not worked #556

aeudes opened this issue Mar 19, 2019 · 2 comments

Comments

@aeudes
Copy link

aeudes commented Mar 19, 2019

On fresh installation on 18.04 with Gazebo9 and ros melodic, the rotors packages are non functional:
when I try to launch any example, the mav did not take off. After investigation, I have find that gazebo complain that:

librotors_gazebo_interface_plugin.so cound not find libmav_msgs.so

The package ros-melodic-rotors-gazebo-plugin did not contain such library but it should as it is defined here :

# Get lists of all .proto files in the msgs directory
file(GLOB msgs msgs/*.proto)
# Finally, generate the .cpp files from the .proto files
PROTOBUF_GENERATE_CPP(PROTO_SRCS PROTO_HDRS ${msgs})
# Create a shared library of protobuf messages (.so extension on Linux platforms)
add_library(mav_msgs SHARED ${PROTO_SRCS})
target_link_libraries(mav_msgs ${PROTOBUF_LIBRARY} gazebo_msgs)
# This causes mav_msgs to be linked with every created library in this file from this
# point forward.
# NOTE: This is deprecated, should be using target_link_libraries instead
link_libraries(mav_msgs)

Please note that this lib is not related to the package mav_msg but is the shared linked library that contained protobuf definition for internal rotors messages.

This previous PR #506 shows the same problem and should correct this issue.

@tomcattiger1230
Copy link

Can you post the caktin build error msg. I think you may have another compile problems

@gsilano
Copy link

gsilano commented Feb 20, 2020

Hi all! As you can see from #506, I solved the problem (at least in my case). Please, take a look at my CrazyS and BebopS repositories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants