Re: [osg-users] Updated osgWorks and osgBullet

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/16/2013 06:54 PM, Paul Martz wrote: > Do you mean OSG svn trunk? There doesn't appear to be a v3.3.1 yet > (didn't see a tag). Yes, trunk (sorry, should have been clearer). > > If trunk, then is this something that is temporarily broken in OS

Re: [osg-users] Updated osgWorks and osgBullet

I see there is a redesign of the osgGA module taking place. If there is reason to believe that this is the last of these changes, then I'm willing to hold up tagging a release while the issue is resolved. But if it's likely that additional such breakages are forthcoming, then holding back on a rel

Re: [osg-users] Updated osgWorks and osgBullet

Do you mean OSG svn trunk? There doesn't appear to be a v3.3.1 yet (didn't see a tag). If trunk, then is this something that is temporarily broken in OSG and will be fixed? On Fri, Nov 15, 2013 at 5:18 PM, Jan Ciger wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 11/15/2013 09:

Re: [osg-users] Disabling Python plugin

On 16 Nov 2013, at 13:12, Robert Osfield wrote: > You should be able to disable the plugin by setting the cmake variable > generated by the find python to OFF. I am away from my dev machine right now > so can’t say exactly what it is called. > > I tried this: -DPYTHONLIBS_FOUND=NO But with

Re: [osg-users] Disabling Python plugin

Hi James, You should be able to disable the plugin by setting the cmake variable generated by the find python to OFF. I am away from my dev machine right now so can’t say exactly what it is called. What was the compile error and what version of python do you have installed? Also what disto are yo

[osg-users] Disabling Python plugin

What’s the official way to disable building the Python osgPlugin? (Indeed, there doesn’t seem to be a generic way to disable arbitrary plugins at all) I was looking for a -DOSG_PLUGIN_PYTHON=OFF or similar, I also tried forcing some of the variables set by FindPythonLibs.cmake to off/false, but