Thanks for the recipe, I managed to compile successfully and the python binding 
is working!!

I was wondering what does the --framework flag do?
they don't mention this flag in the 'man brew' documentation.


here is what I did:
First I followed your steps:

Be sure that /usr/local/bin comes first in your PATH.
brew update
brew rm -f boost cfitsio field3d glew ilmbase jpeg libtiff lcms2 ocio openexr 
scons szip webp python
brew install --framework python

I then uninstalled python26 and re-installed it (just to be sure)
brew rm -f python26
brew install python26

I then followed your last steps
Open a new terminal tab with Command-t (so that your new python gets set into 
your env)
brew install --with-icu boost
brew install oiio


I opened python and imported OpenImageIO without any errors

I also have realized that I never gave you the real python 2.6 setup I use with 
brew.
So here it is. It might be useful for you in your test or documentation:

# get access to old versions in brew to get access to python26 package  (for 
some reason the regular python formula only have 2.6.5 then jumps to 2.7)
# python26 formula is python version 2.6.8
brew tap /homebrew/versions

# build python 2.6.8
brew install python26


So there you have it.
OpenImageIO compiled using brew on a now system python :)

sweet!!!

it there a binary for windows?  I am not sure I will be able to compile on 
windows… I am extremely bad at it



--  
Sylvain Berger
Lead Pipeline TD
Modus FX


On Friday, 3 August, 2012 at 1:40 AM, P. Martin wrote:

> On Aug 2, 2012, Sylvain Berger <[email protected] 
> (mailto:[email protected])> wrote:  
> >  
> >  
> > Hi, thanks for the compile test on your side as well.We are using python 
> > 2.6 because we are building application that needs to run on Maya, Nuke, 
> > Houdini, etc The version software all use python 2.6.
> > Please let me know if you find a fix
> > Thanks
> >  
>  
>  
>  
>  
> Oh that's right, Nuke uses 2.6. Ok so here's what I did to make it work:
>  
>  
> Be sure that /usr/local/bin comes first in your PATH.
> brew update
> brew rm -f boost cfitsio field3d glew ilmbase jpeg libtiff lcms2 ocio openexr 
> scons szip webp python
> brew install --framework python
> Open a new terminal tab with Command-t (so that your new python gets set into 
> your env)
> brew install --with-icu boost
> brew install oiio
>  
>  
> In your case you'll use python26, but do it the same way as a framework.
> I was then able to import OpenImageIO.
>  
> If it doesn't work, gist the output of
>  
> brew --config
> brew doctor
> brew install -v oiio
>  
> If you're comfortable editing the formula, you might insert an exit, e.g.
>  
> system 'make', *args
> system 'exit 1'
> system "make test" if ARGV.include? '--with-tests'
>  
> and `brew -vd oiio` so that it shells out and you can gist the
>  
> build/macosx/CMakeCache.txt
>  
> It's mostly just a matter of removing everything and opening a new
> terminal tab after installing Python. It's possible that boost needed
> to have icu support. Not 100% sure, but there you go. Let us know
> how it works. We always want to iron out the bugs.
> _______________________________________________
> Oiio-dev mailing list
> [email protected] (mailto:[email protected])
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>  
>  
>  


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

Reply via email to