I cloned tom's attempt to reduce history : https://github.com/blobfish/
I'm now in the process of simplifying a bit some things, finding OT, OSG,
Something is still bothering me as OpenSceneGraph is not the only piece of
software osgQt depends on, but also OpenThreads... And the needed
OpenThreads is the one built on Qt's QThreads...
OpenSceneGraph itself is agnostic of the threading library OT is built on.
And it should, however OT is very aware :-)
The only way I see removing Qt altogether from the OpenSceneGraph equation
is to separate OpenThreads also, just like osgQt...
I'm not sure how this would simplify linux distro package creators.
Le ven. 16 sept. 2016 à 18:02, Robert Osfield <robert.osfi...@gmail.com> a
> On 16 September 2016 at 16:17, Mathieu MARACHE
> <mathieu.mara...@gmail.com> wrote:
> > Better approach ! Looks like we have a winner :-)
> Do you want me to apply the script to my osgQt, or do you want to
> apply them to your own.
> Once we feel that osgQt is ready to be used standalone I'd suggest
> forking which ever of our osgQt repo's is most appropriate so that we
> then have a osgQt on the openscenegraph git hub account, I then can
> grant you and who else you want write permission on the project.
> Just let me know how you'd want thing to progress.
> One thing I was planning to do with my osgQt repo was simplifying the
> CMakeLists.txt files to remove all the complex stuff that exists due
> to complexity/history of the OSG project. I have written a few
> NodeKit;s over the years with simplified CMake files which I can use
> as inspiration. Unfortunately these aren't public projects so I can't
> just point you at them as an example.
> osg-users mailing list
osg-users mailing list