Hi Michael, It does sound like there has been a mix up w.r.t which version of BoundingSphere has been built with the OSG i.e. BoundingSphere is typedef'd to BoundingSpheref and BoundingSphered, these are typesdefs against the templated BoundingSphereImp class. Or perhaps you wrappers are assuming one or other.
Robert, On Fri, May 1, 2009 at 10:52 PM, Day, Michael (Mike) (CIV) <[email protected]> wrote: > Howdy, > > > > When building both VirtualPlanetBuilder and some custom PyOSG bindings > against OSG 2.8.0 I get the following linker error (among others): > > > > 1>TaskManager.obj : error LNK2001: unresolved external symbol "public: > virtual class osg::BoundingSphereImpl<class osg::Vec3d> __thiscall > osg::Group::computeBound(void)const " > (?computebo...@group@osg@@ube?av?$boundingspherei...@vvec3d@osg@@@2...@xz) > > > > The “Vec3d” portion of the error is, in fact, correct. There is no such > symbol in all of the OSG libs. There is, however, a > > > > osg@@ube?av?$boundingspherei...@vvec3f@osg@@@2...@xz > > > > (note that it’s a Vec3f). > > > > Is this a difference between OSG 2.6.x and 2.8.0? Is there a solution? > We’ve been able to build our PyOSG bindings against OSG 2.6 successfully > without this issue in the past. > > > > Thanks, > > > > Michael Day > > > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
