On Tue, Jul 5, 2011 at 2:34 PM, Richard Shaw <[email protected]> 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. ... > 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? >
I think there's no reason why an automatic build would need to use the classic Makefile. It generally isn't used on Windows, where make is uncommon. It is, IMO, a nice convenience for those of us who are used to such things, but you can go straight for the cmake stuff if it makes your life easier. (And, it sounds like you are pretty familiar with cmake) > 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? > Last time I actually paid any attention to the build system, there wasn't really a concept of an install target directory. There was build, and then copy the results wherever you wanted. Presumably it's something that could be sorted out without too much trouble. I think the install stuff was sort of being deferred until the project was "mature enough that somebody would actually want to package it for use by others," which has apparently happened. > 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 Is there somewhere specific that you are seeing the hard coded paths? That may help those of us who aren't really up to speed on build issues understand where to look. _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
