gazebosim / gazebosim/gz-rendering
MacOS collision between OGRE1.9 and OGRE2.1
- Dominant language
- C++
- Stars
- 81
- Forks
- 90
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 10
Description
While I was debugging the issue with OGRE + QML on MacOS I founded this issue:
```
objc[37280]: Class OgreConfigWindowDelegate is implemented in both /usr/local/opt/ogre1.9/lib/libOgreMain.1.9.0.dylib (0x14b388dc0) and /usr/local/opt/ogre2.1/lib/libOgreMain.2.1.0.dylib (0x1539eb838). One of the two will be used. Which one is undefined.
```
I talked with @iche033 about this issue in the past:
As for loading the right OgreMain version, I think on ubuntu, we worked around it by installing to different directories, e.g. `/usr/lib/x86_64-linux-gnu/OGRE-2.1` and `/usr/lib/x86_64-linux-gnu/OGRE-1.9.0`. I think we are using the same approach on MacOS but it's not working properly.
Contributor guide
Research direction
Reproduce the Objective-C duplicate-class warning while both /usr/local/opt/ogre1.9/lib/libOgreMain.1.9.0.dylib and /usr/local/opt/ogre2.1/lib/libOgreMain.2.1.0.dylib are present. Compare the macOS installation and loading paths for OGRE 1.9 and 2.1; done means the intended OGRE version loads without the collision warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100