[Bf-committers] EXR Link error?

Galen Beals galenbeals at gmail.com
Sun Nov 22 23:05:31 CET 2009


Hey thanks! Yeah, it looks like this is going to be an issue. I  
couldn't make heads or tales out of the Scons docs to tell you the  
truth. I can't seem to find where it says to identify weather or not  
to use /usr/local/. If you happen to know, that would be great. :)
For now, I just disabled Open EXR in my scons Config. ;)

Thanks again for you help.
-=GB=-

> hi.
>
> On Nov 19, 2009, at 4:11 PM, Galen Beals wrote:
>
> > I've been unable to make a build of blender recently. Ever since I
> > started testing out my own builds of Raman (open source node
> > compositor) I have been getting this same error when compiling  
> Blender
> > 2.5 on OSX using Scons:
>
> This is a linker error. It is finding OpenEXR in /usr/local
> automatically. This path is searched automatically with Scons as a
> feature. It is likely that the version of OpenEXR in /usr/local
> differs from what blender expects or some-such.
>
> > I did update a bunch or dependencies in order to build Ramen and EXR
> > was one of them. But, that one was in /usr/local. As far as I was
> > aware, Blender should be using the one in Blender's "LIBDIR" right?
>
> Scons looks in /usr/local/ automagically. Check the Scons
> documentation to find out the PATHs included by default.
>
> If you plan to distribute your build, be sure to use otool -L on the
> blender binary to see what your resulting binary includes. You may
> also need to manually tweak the link-line to include the OpenEXR
> libraries as static links.
>
> You may wish to try another of the build paths to see if you can
> reproduce the problem.
>
> have a day.yad
> jdpf


More information about the Bf-committers mailing list