2009/5/18 Robert Osfield <[email protected]>: > On Mon, May 18, 2009 at 5:17 PM, Simon Hammett > <[email protected]> wrote: >> I think if you want to check whether you've broken the abi, >> you can check the exported symbols of the dlls/lib. >> >> Breaking the abi means you get different mangled symbols. > > I did look for a 3rd party tool to do the ABI checking for me but came > across nothing. It would be great to have something we could run from > cmake. > > What tools are available for publishing all entry points into a library? >
I think you can just run dumpbin (dumpbin is the VS tool, I'm pretty sure the one for gcc is called the same) on the object files and that lists all the symbols. Once you're into abi freeze, you could use a modified makefile. For each object file, use dumpbin, redirect to a file, build and then diff. You'll get all the private symbols as well which can change without breaking abi, but once you are into abi freeze the number of changes should be pretty low anyway. I suspect in practice it will be fairly easy to tell which symbols are important, especially with a bit of xp with the output. This would work better if the mangled symbols encoded the protection, but for VS, they don't. Don't know about gcc, but I suspect they don't either. After all protection doesn't matter for linking. -- http://www.ssTk.co.uk _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
