Hello everyone,

I'm a Fedora packager (but not an experienced programmer) and I'm
interested in getting OpenImageIO packaged for Fedora, mainly for
blender-cycles but I think oiio could be useful in many other
instances as well.

I need some help with a few things and hopefully you'll bare with me
while I attempt some intelligent questions :)

1. What's up with the source archive file name and embedded directory?

I downloaded the "latest" release from the link at:
https://sites.google.com/site/openimageio/checking-out-and-building-openimageio

Which points to 0.9 and I think should point to 0.10...

Maybe it's a github thing but I assume the 8 digits at the end of the
base name of the archive are some kind of git hash? That was pretty
easy to work around but then it seems that the top level directory of
the archive has a different 8 digit hash...

This makes the spec file for rpmbuild interesting but not really a problem.

2. I'm confused by the Makefile in the root of the source. It appears
to be a plain Makefile which turns around and runs cmake? For Fedora
it's better to use the %cmake macro so that a lot of defaults are set
properly instead of me having to set them manually. I tried just going
into the src directory and doing just that and it appears to work. Are
there any pitfalls to this method I need to be aware of?

3. Would it be difficult to get the cmake configuration to honor
"CMAKE_INSTALL_LIBDIR" so that the library goes in /usr/lib64 on
x86_64 systems rather than usr /usr/lib?

4. Along those lines, how do I get it to build the library with the
proper soname (and symbolic links)?

5. Fedora doesn't allow hard coded paths for libraries (except for
internal libraries). Is there an option to stop this behavior? See:

http://fedoraproject.org/wiki/Packaging:Guidelines#Beware_of_Rpath

I tried the builtin cmake option "CMAKE_SKIP_RPATH" but it didn't seem
to help...

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

Reply via email to