On Wed, Sep 30, 2009 at 5:02 PM, Matthias Kramm <[email protected]> wrote: > On Mon, Sep 28, 2009 at 3:53 AM, Kai Lautaportti > <[email protected]> wrote: >> Here's a patch against setup.py that unifies the environment variable >> overrides in setup.py and adds some additional logic to it. >> >> The main changes are >> >> - all variables prefixed with SWFTOOLS_ to avoid conflicts with >> other variables >> - option to disable building of either Python module (gfx and/or SWF) > > I took a look a the patch. Question: Why do you need conditional > compilation of gfx/SWF? > Is that to prevent compile problems with one or the other, or because > you only need one and > want to compile faster?
We only use gfx ourselves and linking SWF against PIL (_imaging.so) has turned out problematic on OSX. By default the PIL .so libraries are created as bundles on OSX which cannot be linked against. I was able to manually hack PIL so that the libs are built using -dynamiclib instead of -bundle which allowed the linking but in our case it is far easier to just disable SWF alltogether. Also, I recall hearing that you were thinking about deprecating the SWF module.. is that correct? cheers, Kai -- CTO Kai Lautaportti Hexagon IT Oy [email protected] www.hexagonit.fi +358-40-486-9803
