> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:osg-users- > [EMAIL PROTECTED] On Behalf Of Robert Osfield > Sent: 08 January 2008 09:12 > To: OpenSceneGraph Users > Subject: Re: [osg-users] Which version of the Collada DOM does OSG use? > > Hi Steven, > > On Jan 7, 2008 8:33 PM, <[EMAIL PROTECTED]> wrote: > > Ok, I'm still a bit confused about whether the Collada plugin is > > supposed to use the development version of the DOM or the last stable > > release (1.3 from 30 March 2007). > > > > It'd be more sensible to use the last > > stable release of the DOM, but looking at the CMakeLists.txt file leads > > me to believe that (at least on Linux) the plugin is using the > > development version of the DOM. > > The COLLADA plugin is contributed to by a range of developers, as its > relatively large plugin and I'm swamped with other work I have stepped > back and let those contributing to the plugin dictate its ongoing > development. The version that the OSG plugin works with has shifted > around as OSG contributors catch up with various points in time for > the COLLADA plugin, sometimes stable sometimes development. A bit > confusing yes, even I am not totally clear on it at all times. > > Ideally once we get to stable versions of the OSG, we do need to > settle upon stable version of COLLADA. >
[Roger James] Robert, Steven, I agree with the statement the OSG should use the last stable release of the "COLLADA DOM 1.4.1" package. I have avoided the use of just the word DOM because I think that is where some of the confusion comes from. The last stable release is tagged "COLLADA 1.4.1 DOM 1.3.0". When the "COLLADA 2.0 DOM" package appears we should pick it up at that next convenient release. Historically I have always built against a SVN checkout of Collada, but not necessarily a recent one. This was because I needed some bug fixes that went in pre "COLLADA 1.4.1 DOM 1.3.0". I did not change my build system after that Collada release, and I suspect others did not do so either. This is because I have always had to hack or bypass the OSG CMake stuff to make it work in my environment. But I do not think there are code changes in the Collada package post 1.3.0 that are demanded by the plugin. If a particular user does need a later svn version then I think it is up to them to make the local changes necessary to incorporate it into their environment. However if we are to standardise on the 1.3.0 there is problem in that the 1.3.0 Collada build system does not produce separately named release and debug libraries and dlls on windows (I do not know if this is case on Linux). So unless we can persuade Steve to make a quick fix 1.3.1 release that fixes this on the 1.3.0 code base, then we probably cannot make an automatic out of the box OSG CMake build system for the plugin. I suggest that a way forward is for us to assume that there will be separately named debug and release libraries and dlls, either from local hacking of the collada build system at 1.3.0, or by an interim release. Then find someone who is willing to update the OSG Collada plugin CMake files to work with the chosen solution, including the work necessary to handle the cascade of additional static library dependencies that a statically linked build of the Collada DOM build needs. The next problem then being that if other contributors to the osg collada plugin are like me, then they have little real knowledge of the CMake build system, and would prefer not to have to acquire it :-(. Roger _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
