Maybe the DOM 2.2 binaries could go into the 3rdparty folder or repository? that way the plugin becomes 'out of the box' like png and freetype or do we want a limited set of 3rdparty binaries?
About the 2.8.3 release: I recently updated sources to use the new manipulators in 2.9.7 . Is there a stable release to be expected that include these (nice!) improvements? I wouldn't mind these changes in 2.8.3 but other users of the old manipulator code will have to change some code. Groetjes, René 2010/3/20 Jean-Sébastien Guay <jean-sebastien.g...@cm-labs.com> > Hi Chris, > > > Yes, but building the DAE plugin at all is complicated. Have you done it >> before? >> > > That was my impression until last Friday, too. I was proven wrong by doing > it. It was literally a 3 step process. > > 1. Get the DOM 2.2 zip file from sourceforge > 2. Open the solution file in there and build all configurations > 3. Point CMake at the DOM directory and optionally check the USE_STATIC_DOM > flag, generate and then compile the plugin > > (sure that last step is more than one atomic operation, but running CMake > to configure and generate build files and then using those to build OSG is > pretty routine :-) ) > > Were you talking about other platforms? I don't see why it should be harder > on Linux, given for almost any other dependency it's actually simpler on > Linux thanks to package managers on almost any distribution. > > > J-S > -- > ______________________________________________________ > Jean-Sebastien Guay jean-sebastien.g...@cm-labs.com > http://www.cm-labs.com/ > http://whitestar02.webhop.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
