Re: [osg-users] Linker error with VirtualPlanetBuilder
Hi Mike, As Paul mentions the OSG now sets up the values that are used by default for things like floating matrices and bounding boxes/spheres. The settings are stored in the include/osg/Config file. This file is automatically generated by CMake when you configure the build system. It sounds like somehow you wrappers are missing this or ignoring it in some way. Robert. On Mon, May 4, 2009 at 10:16 PM, Day, Michael (Mike) (CIV) ma...@nps.edu wrote: OK, Got it. In version 2.8.0, in the BoundingSphere header file there is this code at the bottom: #ifdef OSG_USE_FLOAT_BOUNDINGSPHERE typedef BoundingSpheref BoundingSphere; #else typedef BoundingSphered BoundingSphere; #endif OSG 2.8.0 ships built with float (rather than double) BoundingSpheres. A very similar problem exists for BoundingBoxes. Because of this, apps that build against it need to be careful -- either that or perform a custom build of OSG, which we don't want to require users of our PyOSG to do. Our hack was to set preprocessor definitions OSG_USE_FLOAT_BOUNDINGSHPERE and OSG_USE_FLOAT_BOUNDINGBOX in our bindings project. Cheers, Michael Day -Original Message- From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Robert Osfield Sent: Saturday, May 02, 2009 1:02 AM To: OpenSceneGraph Users Subject: Re: [osg-users] Linker error with VirtualPlanetBuilder 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) ma...@nps.edu wrote: Howdy, When building both VirtualPlanetBuilder and some custom PyOSG bindings against OSG 2.8.0 I get the following linker error (among others): 1TaskManager.obj : error LNK2001: unresolved external symbol public: virtual class osg::BoundingSphereImplclass 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 osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Linker error with VirtualPlanetBuilder
OK, Got it. In version 2.8.0, in the BoundingSphere header file there is this code at the bottom: #ifdef OSG_USE_FLOAT_BOUNDINGSPHERE typedef BoundingSpheref BoundingSphere; #else typedef BoundingSphered BoundingSphere; #endif OSG 2.8.0 ships built with float (rather than double) BoundingSpheres. A very similar problem exists for BoundingBoxes. Because of this, apps that build against it need to be careful -- either that or perform a custom build of OSG, which we don't want to require users of our PyOSG to do. Our hack was to set preprocessor definitions OSG_USE_FLOAT_BOUNDINGSHPERE and OSG_USE_FLOAT_BOUNDINGBOX in our bindings project. Cheers, Michael Day -Original Message- From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Robert Osfield Sent: Saturday, May 02, 2009 1:02 AM To: OpenSceneGraph Users Subject: Re: [osg-users] Linker error with VirtualPlanetBuilder 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) ma...@nps.edu wrote: Howdy, When building both VirtualPlanetBuilder and some custom PyOSG bindings against OSG 2.8.0 I get the following linker error (among others): 1TaskManager.obj : error LNK2001: unresolved external symbol public: virtual class osg::BoundingSphereImplclass 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 osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Linker error with VirtualPlanetBuilder
These should be defined in the osg/Config header, so if you app #includes it, you should get the right definitions (assuming you include the same header that OSG was built with). Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com +1 303 859 9466 -Original Message- From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Day, Michael (Mike) (CIV) Sent: Monday, May 04, 2009 3:17 PM To: OpenSceneGraph Users Subject: Re: [osg-users] Linker error with VirtualPlanetBuilder OK, Got it. In version 2.8.0, in the BoundingSphere header file there is this code at the bottom: #ifdef OSG_USE_FLOAT_BOUNDINGSPHERE typedef BoundingSpheref BoundingSphere; #else typedef BoundingSphered BoundingSphere; #endif OSG 2.8.0 ships built with float (rather than double) BoundingSpheres. A very similar problem exists for BoundingBoxes. Because of this, apps that build against it need to be careful -- either that or perform a custom build of OSG, which we don't want to require users of our PyOSG to do. Our hack was to set preprocessor definitions OSG_USE_FLOAT_BOUNDINGSHPERE and OSG_USE_FLOAT_BOUNDINGBOX in our bindings project. Cheers, Michael Day -Original Message- From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Robert Osfield Sent: Saturday, May 02, 2009 1:02 AM To: OpenSceneGraph Users Subject: Re: [osg-users] Linker error with VirtualPlanetBuilder 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) ma...@nps.edu wrote: Howdy, When building both VirtualPlanetBuilder and some custom PyOSG bindings against OSG 2.8.0 I get the following linker error (among others): 1TaskManager.obj : error LNK2001: unresolved external symbol public: virtual class osg::BoundingSphereImplclass 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 osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph. org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] Linker error with VirtualPlanetBuilder
Howdy, When building both VirtualPlanetBuilder and some custom PyOSG bindings against OSG 2.8.0 I get the following linker error (among others): 1TaskManager.obj : error LNK2001: unresolved external symbol public: virtual class osg::BoundingSphereImplclass 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 osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Linker error with VirtualPlanetBuilder
It might be a version issue. Are you sure that your VPB version is compatible with your OSG version? For example, I wouldn't expect current svn head of VPB to be compatible with OSG v2.6... Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com http://www.skew-matrix.com/ +1 303 859 9466 _ From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Day, Michael (Mike) (CIV) Sent: Friday, May 01, 2009 3:52 PM To: osg-users@lists.openscenegraph.org Subject: [osg-users] Linker error with VirtualPlanetBuilder Howdy, When building both VirtualPlanetBuilder and some custom PyOSG bindings against OSG 2.8.0 I get the following linker error (among others): 1TaskManager.obj : error LNK2001: unresolved external symbol public: virtual class osg::BoundingSphereImplclass 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 osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Linker error with VirtualPlanetBuilder
Paul, Thanks for the quick response. Current svn trunk of VPB should build find under 2.8.0, though, right? I haven't tried to build VPB with OSG 2.6, only our custom PyOSG. My point was only that the linker errors we're getting are identical for both projects. Thanks, Mike - Paul Martz pmartz at skew-matrix.com mailto:osg-users%40lists.openscenegraph.org?Subject=Re%3A%20%5Bosg-user s%5D%20Linker%20error%20with%20VirtualPlanetBuilderIn-Reply-To=%3C5DA29 666083C4982B7E055D55DD1A378%40supreme%3E Fri May 1 15:43:54 PDT 2009 * Previous message: [osg-users] Linker error with VirtualPlanetBuilder http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/ 2009-May/027369.html * Next message: [osg-users] Set view direction http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/ 2009-May/027370.html * Messages sorted by: [ date ] http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/ 2009-May/date.html#27373 [ thread ] http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/ 2009-May/thread.html#27373 [ subject ] http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/ 2009-May/subject.html#27373 [ author ] http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/ 2009-May/author.html#27373 It might be a version issue. Are you sure that your VPB version is compatible with your OSG version? For example, I wouldn't expect current svn head of VPB to be compatible with OSG v2.6... Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com http://www.skew-matrix.com/ +1 303 859 9466 _ From: osg-users-bounces at lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.o rg [mailto:osg-users-bounces at lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.o rg ] On Behalf Of Day, Michael (Mike) (CIV) Sent: Friday, May 01, 2009 3:52 PM To: osg-users at lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.o rg Subject: [osg-users] Linker error with VirtualPlanetBuilder Howdy, When building both VirtualPlanetBuilder and some custom PyOSG bindings against OSG 2.8.0 I get the following linker error (among others): 1TaskManager.obj : error LNK2001: unresolved external symbol public: virtual class osg::BoundingSphereImplclass osg::Vec3d __thiscall osg::Group::computeBound(void)const (?computeBound at Group http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.o rg @osg@@UBE?AV?$BoundingSphereImpl at VVec3d http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.o rg @osg@@@2 at XZ http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.o rg ) 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?$BoundingSphereImpl at VVec3f http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.o rg @osg@@@2 at XZ http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.o rg (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 osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
