Re: [Visualpython-users] VPython on OS X, steps forward and otherwise

[Martin C. <cos...@wa...>]

Dethe Elza wrote:
> On 30-Nov-06, at 12:17 PM, Martin Costabel wrote:
> 
>> Yes, that's what you get when you link cvisualmodule.so with Fink's  
>> libboost_python.dylib that was compiled with the system python2.3.  
>> To work around this, you can link with the static libboost_python.a  
>> by changing "-lboost_python" to "/sw/lib/libboost_python.a" at the  
>> right place in src/Makefile.in.
> 
> That did it!  Thanks for being patient with me and repeating your  
> good advice until I see it.  I now have a build of visual that  
> supports transparency!

I have now made and committed a new revision of Fink's boost1.33 
package, version 1.33.1-1007. It builds libboost_python.dylib using 
Fink's python, no longer with the system python framework. This avoids 
the crash we were talking about. In fact, the new libboost_python.dylib 
can be built with any one of Fink's python versions 2.3, 2.4, or 2.5. 
The resulting libraries are, for all intents and purposes, identical, as 
far as I can tell, and they can be used with any of these python versions.

In particular, I was able to compile the current vpython-core2 CVS 
sources (beta10) without any patches. The entire incantation was, as 
noted before:

   sh ./autogen.sh
   export 
PKG_CONFIG_PATH=/sw/lib/fontconfig2/lib/pkgconfig:/sw/lib/xft2/lib/pkgconfig:/sw/lib/freetype219/lib/pkgconfig
   ./configure --prefix=/sw
   make

-- 
Martin