On Tue, Jul 5, 2011 at 11:06 PM, Chris Foster <[email protected]> wrote: > SOVERSION is meant to be the API version, so I guess it should really be 0.9 > if > you're building the 0.9 branch. (For OIIO, the api has been liable to change > between minor versions, but is stable for patch releases.) The build system > will already set the VERSION option correctly to 0.9.3 (if you're using that > version). > > Looking through the code, I see that the SOVERSION support is an "interesting" > hack: It not only sets the SOVERSION of libOpenImageIO, but also adds an extra > namespace with name based on the SOVERSION, so you'll get all sorts of odd > things if you change it without a "make clean". In addition you can't > currently use the '.' character because that's not a valid C++ identifier!
Well that explains a a lot. Rpmbuild typically does remove previous builds but I'm only telling it to build through the compile or install stage so it's leaving the build directory intact which seems to be causing some of my problems. > While I'm sure this makes perfect sense for studio usage it's going to have to > be modified for linux packaging purposes. I've made a patch which should > hopefully just "do the right thing" for you and allow you to forget about > setting SOVERSION. The patch is at: > > https://github.com/OpenImageIO/oiio/pull/118 I followed the link but didn't see an easy way to get a unified patch. There's probably a way but I'm not as familiar with git/github as I am with svn. I know git is supposed to be much easier for developers but svn is a lot easier for packagers. :) Thanks, Richard _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
