On Sun, Jul 10, 2011 at 11:55 PM, Richard Shaw <[email protected]> wrote:
>> * What is your latest cmake configuration line, including all -DBLAH options?
>
> + /usr/bin/cmake -DCMAKE_VERBOSE_MAKEFILE=ON
> -DCMAKE_INSTALL_PREFIX:PATH=/usr
> -DCMAKE_INSTALL_LIBDIR:PATH=/usr/lib64
> -DINCLUDE_INSTALL_DIR:PATH=/usr/include
> -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc
> -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64
> -DBUILD_SHARED_LIBS:BOOL=ON -DCMAKE_SKIP_RPATH:BOOL=TRUE
> -DPYLIB_INSTALL_DIR:PATH=/usr/lib64/python2.7/site-packages
> -DINSTALL_DOCS:BOOL=OFF -DUSE_EXTERNAL_PUGIXML:BOOL=TRUE ../src

Using this command seems to work for me (after an update to the RPATH handling
so that man pages could still be generated when CMAKE_SKIP_RPATH was
specified).

Oh, I see the problem.  The line

libOpenImageIO.so.0.10.0: undefined reference to
`OpenImageIO::v0_10::pugi::xml_node::child_value(char const*) const

means that your build is still finding the OIIO version of pugixml.hpp rather
than finding the system version, ugh.  It worked on my system only because I
had install pugixml into its own directory (not into /usr/lib) and was able to
give an include path other than the standard one.

I think this means I've got as far as I can without moving the oiio version of
pugixml.hpp somewhere other than the main include directory.

@Larry: thoughts?  My only idea is to have a separate include directory for
the external libraries which OIIO has bundled, something like
include/thirdparty, and conditionally add that to the include path in the build.

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

Reply via email to