Hi Michael, On 21 July 2013 12:09, Michael Brandl <[email protected]> wrote:
> Hi Robert, > > thanks for the changes, now both checking out and building OpenThreads > 2.3.0 works like a charm. > > The fix in http://forum.openscenegraph.**org/viewtopic.php?t=5571&** > highlight=2.3.0<http://forum.openscenegraph.org/viewtopic.php?t=5571&highlight=2.3.0>was > not needed. > > > Out out curiosity, I also tried to build 2.6.0. > > Here, I ran into CMake-problems > 1. the one described in the link above about the missing > PlatformSpecifics/Windows/Open**ThreadsVersionInfo.rc.in<http://OpenThreadsVersionInfo.rc.in> > , > 2. another one about a missing > packaging/pkgconfig/openthread**s.pc.in<http://openthreads.pc.in> > . > > Copying the ones from osg 3.0.1 into the corresponding folders in > OpenThreads solved the problems, and building worked well from then on. > I had to make this change to the new OpenThread-3.2 branch, just check the OpenThreads-2.6.0 tag I see that the pkgconfig directory isn't there so I'll add this from svn/trunk Could you test out OpenThreads-2.6.0 to see it works now. > I don't know the backgrounds of having OpenThreads in a separate > repository, but it is certainly useful to being able to build and use > OpenThreads without the whole rest of osg. The question is of course how > this is most easily implemented and maintained; another variant might be to > make it a build option in cmake in osg rather than a separate repository. > OpenThreads was developed for the purpose of adding threading to the OSG and was originally managed separately, but the original author gave up managing it so the responsibility fell to me. I managed it separately for a number of years but for the OSG-2.0 series I moved OpenThreads to be part of the core OSG distribution as it was a right pain for all OSG users having to jump through loops with external dependencies that had no reason to exist externally except origins of the project. OpenThreads has never had a separate community and almost no users that use it outwith the OSG. Those who do occasional (perhaps one developer per once every five years) turn up to say that they have used OpenThreads separately have never helped with support of OpenThreads. > > It might be a good idea to set up an automatic test build in either case, > because then problems like these are much earlier caught, which often makes > it easier to fix them. I'm not about to add extra work for very occasional issue with OpenThreads being used externally from the OSG, if users wish to use OpenThreads separately from the OSG then it's really down to them to report problems appear and get reported I'll fix them. Please remember I'm the project lead of the OSG and this is my focus. Longer term for the OSG I expect to see OpenThreads replaced by std::thread that is now available in C++11. Robert.
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
