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

Potential conflicts for packages with names ending in _devel or _install #532

Closed
scpeters opened this issue Oct 9, 2013 · 0 comments
Closed
Assignees
Labels

Comments

@scpeters
Copy link
Contributor

scpeters commented Oct 9, 2013

The build folder for plain cmake projects can have a suffix of _devel or _install appended depending on the type of build.

This can lead to a conflict depending on package names. For example, the plain cmake project gazebo would conflict with a catkin package named gazebo_devel.

I don't expect _install to be a common suffix for packages, but I could imagine _devel being used. It's a minor issue, but there's probably some easy workarounds to make conflicts less likely, like putting one or more trailing _'s in the build folder names for plain cmake packages.

@ghost ghost assigned dirk-thomas Oct 10, 2013
cwecht pushed a commit to cwecht/catkin that referenced this issue Mar 20, 2018
* OgreSlice has a slice_id.

This is necessary because we will have multiple OgreSlices
and Ogre requires unique names for textures and other entities.

* Visualize both high and low res slices.

Adds checkboxes to the rviz plugin to show high and low
resolution slices.
DrawableSubmap now holds a vector of OgreSlices and
decides which slices are visible.

* Corrections. Move slice visibility to OgreSlice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants