Hi Julia, The number is the SO version number of the release, each time the ABI changes between dev releases I increment the SO version number. The SO version number is included to make sure that your application links at runtime to the same library that it compiled against. So if you compiled against OSG-3.0.0 but then install OSG-3.2.0 you won't have your application accidentally link to OSG-3.2 at runtime. However, if you install to binary compatible release then you can run against this without problems. For instance the up coming OSG-3.2.1 will have the same SO version and library naming as OSG-3.2.0 so you'll be able to drop in 3.2.1 in without needing to recompile.
Robert. On 20 October 2013 13:37, Julio Jerez <[email protected]> wrote: > Hi > when I start my project I download this sdk > > .Zip file containing source code > :releases/OpenSceneGraph-3.0.1/source/OpenSceneGraph-3.0.1.zip > OpenSceneGraph-3.0.1.zip md5sum c43a25d023e635c3566b2083d8e6d956 > > now I sync to svn checkout > http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk > and get this current version > > but when I build the solution with visual studio the out libraries shave a > very different prefix name > > the 3.01.zip had prefix osg80- > and the svn versions has prefix osg111 > > is there a reason for this? > which version is the current? or should I be using? > > Thank you > Julio > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
