gazebo 1.9 does not set LD_LIBRARY_PATH for plugins

[osrf-migration]

Original report (archived issue) by John Hsu (Bitbucket: hsu, GitHub: hsu).

---

gazebo_2.0 setups up setup.sh.in to update LD_LIBARAY_PATH, but gazebo 1.9 does not. We should add back

export LD_LIBRARY_PATH=@CMAKE_INSTALL_PREFIX@/@LIB_INSTALL_DIR@/gazebo-@GAZEBO_VERSION@/plugins:${LD_LIBRARY_PATH}

and remove the release overlay.

But ultimately, we should push all the pluigns install target to top level ${CMAKE_INSTALL_PREFIX}/${LIB_INSTALL_DIR}/ (rather than ${CMAKE_INSTALL_PREFIX}/${LIB_INSTALL_DIR}/gazebo-${GAZEBO_VERSION}/plugins/) and rename the plugins to be prefixed by Gazebo or similar.

[osrf-migration]

Original comment by John Hsu (Bitbucket: hsu, GitHub: hsu).

---

• changed priority from "major" to "blocker"

upgrading as this will break for gazebo_1.9 users when installing from source.

[osrf-migration]

Original comment by John Hsu (Bitbucket: hsu, GitHub: hsu).

---

just referencing to a similar pull request where the install target directory for install library files are pushed up to system location.

[osrf-migration]

Original comment by John Hsu (Bitbucket: hsu, GitHub: hsu).

---

fix for first part in pull request #844

[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).

---

Maybe we can close this since gazebo 1.9 is EOL?

[osrf-migration]

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

---

• Edited issue description* set component to "plugins"

[osrf-migration]

Original comment by Shane Loretz (Bitbucket: Shane Loretz, GitHub: sloretz).

---

• changed state from "new" to "wontfix"

Gazebo 1.9 is EOL