Hi bouffa,
thx for this info! I never knew that there was a difference between trunk
and branch not suspected such a think.
How, I understand that the developer version is the trunk and the released
stable versions are branches.
bouffa wrote:
Hi Allen,
Hi Allen,
usual naming convention is to call trunk to the current content of the
working base in svn repsitory. This means, trunk is something were all
changes/patches are applied to. After some time, trunk is get tagged,
branched, and new release is published. In several cases the so tagged
Thank you Art. :)
I understand and it does appear that the trunk version of OSG has a different
API from the stable release version, 2.8.3.
I'll be happy to stay with osg 2.8.3 and osgPPU 0.4. This combination works
very well on both linux and windows. I'll upgrade my version of osgPPU
Hi Art -- I'm a little confused. Maybe we're not communicating clearly.
Art Tevs wrote:
As for osgPPU it is not only the getOrCreateGLBufferObject() which don't work,
but also much more things. I tried yesterday to bring combine current trunk
version of osgPPU with osg 2.8 and that didn't
Hi Paul,
no, I do not have to change anything to build for 2.8.3 It is just that I added
some small and big features to osgPPU. For example current svn trunk version
has new Units (UnitInOutRepeat - for iterative/loop subgraphs), new examples
and some bugfixes. I cannot use that new unit in
Hi Art,
I decided to start a new thread on this issue. It's a biggy for me.
here's what I get every time I attempt to compile the svn version of osgPPU
agains osg 2.8.3:
Code:
[al...@nlosdemobox:]$ make
Scanning dependencies of target osgPPU
[ 2%] Building CXX object
O, one other note. I have the exact same issues under Windows XP.
--Allen
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=27098#27098
___
osg-users mailing list
osg-users@lists.openscenegraph.org
Allen Saucier wrote:
[al...@nlosdemobox:]$ make
Scanning dependencies of target osgPPU
[ 2%] Building CXX object src/osgPPU/CMakeFiles/osgPPU.dir/Unit.o
In file included from /home/allen/projects/osgPPU/src/osgPPU/Unit.cpp:17:
/home/allen/projects/osgPPU/include/osgPPU/Unit.h: In member
Hi Allen,
hmm, very strange, current osgPPU version compiles against osg 2.9.8 which is
the developer version number of 2.8.3 branch, as I think.
The compilation error is about include files, did you checked that osg 2.8.3
also has reinstalled your include files.
I will check this today or
Ok, then it explains why it does not compile. Yes, svn trunk of osgPPU tracks
the svn trunk of OSG.
Hmm, I wonder how to handle different osg branches in future. I mean if again
something like this happens, then I had either to create additional branch in
osgPPU repository to track with the
Gentlemen, thank you.
Now I understand. But, I still have an issue. I downloaded osg 2.8.3 from the
Osg website
as shown in the attached pic 1. I used the svn link as shown. Is this link
the trunk of osg 2.8.3? Or a branch? i can not tell.
I did the same with osgPPU. pic 2
From my
Hi Allen,
http://www.openscenegraph.org/projects/osg/wiki/Downloads
You are using the svn of the 2.8 branch (stable release). The trunk is a
developer release (at the end of the web page). To get svn trunk of osg,
check this link :
http://www.openscenegraph.org/projects/osg/wiki/Downloads/SVN
Art Tevs wrote:
Ok, then it explains why it does not compile. Yes, svn trunk of osgPPU tracks the svn trunk of OSG.
Hmm, I wonder how to handle different osg branches in future. I mean if again
something like this happens, then I had either to create additional branch in
osgPPU repository to
Allen Saucier wrote:
http://forum.openscenegraph.org//files/screenshot2_903.png
The statement in this image implies that svn trunk of osgPPU is compatible with
the latest stable release of OSG. This is not correct.
It looks like the osgPPU 0.4 tag should be compatible with OSG 2.8.x. Maybe
Hi Art, Paul,
My external projects osgWorks and osgBullet are compatible with OSG
2.6.1 and later. osgWorks contains version-specific code in only two
places (to handle the OSG API changes in Registry and Traits that
occurred in OSG 2.6.0 and 2.8.0 respectively). And osgBullet contains no
Hi Paul,
you are right, current svn trunk of osgPPU is not compatible with osg 2.8.3,
thats true. But what I mean is what should external project developers do, if
there is a branch with different API in the osg svn repository?
For example, current osg developer version is 2.9.8 which is not
Art Tevs wrote:
However if some time ago there was a split into another branch it might became painful to have an external NodeKit compatible with all official osg branches that exists. I mean 2.8.3 is based on 2.8, so between 2.8 and 2.9 there was an API change, this is ok. However both versions
17 matches
Mail list logo