Comment 1 for bug 83989

Revision history for this message
Lukas Fittl (lfittl) wrote :

This is due to the way how libOgrePlatform.so is currently handled, as it does not have a proper SONAME at the moment.

Solutions to this problem are either concerning upstream to properly manage an SONAME for this library as well, or to manually patch an SONAME into it. The first one seems more appropriate to me, but requires further investigations from my side if this is really the correct way to do it, and after that there is the work of convincing upstream that it is important. So I guess this will be solved for the 1.4 release of Ogre.