On Oct 29, 2011, Stephen Parker <[email protected]> wrote:
>
> I'm curious to know if anyone has been building OIIO for OSX using
> non-standard locations for dependent libraries
> ...snip...
> Basically, I modify the top-level Makefile with:
>
>MY_CMAKE_FLAGS += -DILMBASE_HOME=/opt/3ps/ilmbase/1.0.1
I understand how difficult it is to deal with the CMake docs. There should be
a top 10 most useful
things you can do to affect your build. Luckily after having read thru some
pages like that, and
having other example formula from Homebrew to read how they did it, I can now
offer you a few
useful methods to help CMake find your environment.
The first and most useful method, by a long shot, is -DCMAKE_PREFIX_PATH. If
you set that,
it gets appended to any search path the build looks into for libraries and
includes. It is most
often used form the command line like this,
mkdir macbuild
cd macbuild
cmake -DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_PREFIX_PATH=/opt/3ps
and it would expect to find the usual /opt/3ps/include and /opt/3ps/lib
In this build, it looks like you modify the Makefile, but try this options, i.e.
MY_CMAKE_FLAGS += -DCMAKE_PREFIX_PATH=/opt/3ps
If that doesn't work for all your libs, you can try to set the build-specific
environment variables
before you run make, i.e. in bash I would do this (might have to use
/opt/3ps/ilmbase )
export OPENEXR_HOME=/opt/3ps
export ILMBASE_HOME=/opt/3ps
make
Good luck with your mac. When I get my Homebrew formula finished, you will be
able to build and
install oiio + all deps + oiio-images with one command, brew install
openimageio, and no sudo.
It works now, but I'm checking on my testsuite fails before I upload it.
2bits
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
