Hi Alberto, Thanks for the link. I will need to try the ABI compliance checker out. Right now I have enough on my plate this finish this week so learning and using and new tool isn't something I can manage. If others already know how to use it then I'd appreciate checking 3.2.1-rc6 against 3.2.0.
For the warning fix that required addition of virtual destructor, I've decided not to apply this fix as it looks likely that it could break the ABI, it certainly isn't worth the risk just to address a compiler on a 4 year old rev of Fedora. Thanks, Robert. On 3 July 2014 15:37, Alberto Luaces <[email protected]> wrote: > Robert Osfield writes: > > > Hi Tom, et. al, > > > > > > On 3 July 2014 13:41, Jolley, Thomas P wrote: > > > > [...] > > >> > > > > > > Thanks. All are easy warnings to fix, but would adding a virtual > > destructor change the ABI? If it changes the ABI then I don't feel it's > > appropriate to merge the change into the OSG-3.2 as my intention is for > > 3.2.1 to remain binary compatible with 3.2.0. > > > > Thoughts on this everyone? > > In order to be completely sure, one may use the "ABI compliance checker" > tool (http://ispras.linuxbase.org/index.php/ABI_compliance_checker) and > check against the current version, listed among others at > > http://upstream-tracker.org/versions/openscenegraph.html > > In the "show log" switch, the configuration file is shown, and > additionally, how to use the program to perform the checks. > > -- > Alberto > > _______________________________________________ > 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
