I fixed the web pages to reflect the new stable release (0.10), thanks for
catching that.
We use CMake for our cross-platform builds. The 'Makefile' is redundant, there
for the sake of those of us who have 20 years of typing 'make' as habit and
hate that CMake wants you to change into the build directory and invoke from
there. It's just a wrapper for the right cmake commands.
As far as the SONAME and linkage issues, it looks like there's a thread in
progress to address those issues; hopefully the main stakeholders in naming and
linking conventions and those who know CMake details are getting their heads
together to come up with a solution. I'll go along with anything that works
for everybody.
And I think it would be great to have a Fedora package.
I'd also really really love a build server(s) that we can use to make packaged
builds for the various platforms for our major releases -- especially Windows,
which is both tricky and a platform that many of our key developers (including
myself) don't have easy access to. I wish GitHub provided it as a paid add-on.
If anybody knows if a low-hassle, reasonably priced build-hosting service
(say, that could check out a GH repo and compile it on several platforms, then
post the resulting binaries somewhere, let us know.
-- lg
On Jul 5, 2011, at 2:34 PM, Richard Shaw wrote:
> 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
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
