Hi Richard,

On Wed, Jul 6, 2011 at 9:35 AM, Richard Shaw <[email protected]> wrote:
> On Tue, Jul 5, 2011 at 4:34 PM, Richard Shaw <[email protected]> wrote:
>> 4. Along those lines, how do I get it to build the library with the
>> proper soname (and symbolic links)?
>
> Ok, I think I've figured this one out. I can set the cmake option
> SOVERSION but it seems to cause a lot of these:
>
> error: too many decimal points in number
>
> I'm trying "-DSOVERSION:STRING=0.9.3"
>
> Any ideas?

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!

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

~Chris
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to