Gazebo's find_package rules do no expose plugins

[osrf-migration]

Original report (archived issue) by Tully Foote (Bitbucket: Tully Foote, GitHub: tfoote).

---

gazebo should expose the optional components like other libraries with the COMPONENTS keyword, in particular the plugin libraries.

So it would be like: find_package(gazebo REQUIRED COMPONENTS Core CameraPlugin)

This would allow the find_package to correctly populate the GAZEBO_LIBRARIES variable to include the plugins instead of requiring the downstream user to call

set_target_properties(TARGET_NAME PROPERTIES LINK_FLAGS "${ld_flags}")

for every target. And then you have to hard code the plugin library name in the TARGET_LINK_LIBRARIES call.

The default if you don't pass any components is that you get all components. This is patterend off of Boost and several other libraries.

[osrf-migration]

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

---

• set version to "all"

[osrf-migration]

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

---

• Edited issue description* set component to "plugins"