Hi Peter, As far as I'm aware osgPython is still an active project, the project was only announced back in late 2006. Contact the lead to see the current status. Its open source so you'll be able to contribute to it, and even pick the project up if needs be.
Robert. On 1/17/07, Peter Gebauer <[EMAIL PROTECTED]> wrote:
Thanks for the swift reply! Have you made or are you considering making your own bindings for OSG? I just haven't managed to make it build, The problem could simply be that the bindings aren't working well with the latest OSG-release. Or any other problem that I'm not aware of. The development of osgPython (and PyOSG forks) seem to have stagnated lately. Since there seems to be a general interrest of including osgPython as a "standard" OSG extension, possibly even a part of the 1.3 release, I would be eager to assist with what little I can do, like extensive testing. Even if it's not osgPython, but some other clever Python binding that uses osgIntrspection, I would be thrilled to help out. /Peter On 2007-01-16 (Tue) 11:50, Robert Osfield wrote: > Hi Peter, > > I haven't downloaded and played with osgPython yet, but I'd raise the > question about the importance of boost for osgPython. > osgIntrospection doesn't need it, so perhaps osgPython could be > changed to remove the boost dependency. I have no clue as how much > work this would be though. > > FYI, genwrapper which builds the wrappers uses boost, but since this > is an external tool that is only required when you update the wrappers > (as I do from time to time) the dependency is pushed on to all users. > _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/