On 20/10/09 06:33, Chris Mohler wrote:
On Mon, Oct 19, 2009 at 11:21 PM, ~suv <suv-sf@...58...> wrote:
Just tested and put the lxml and numpy for python 2.5 that I had compiled with MacPorts into the 0.47pre4 bundle and Inkscape loads them fine and reports lxml version 2.2.2 :)
i.e. I could zip them up and add the zip to your bug report for you or him to download _if_ your client runs 10.5.8 (i386) with python 2.5 or python 2.6 installed. He just has to unzip them and copy the folders into the bundle, no need to build them on his machine. If he still uses Tiger OS X 10.4.x or has a PPC processor then I can't help.
I haven't built a DMG before - so I would prefer a simple zip...
Back on list - just for posterity :)
That is good news - I'm still waiting to hear back on his OS X version and arch. I'll report back once I have some more info either way.
Arrgh - I was too fast to respond or too sloppy in testing! Obviously the path to the python installation (inside the MacPorts tree) is hardcoded into the modules - if I rename the installation directory (I have not used the default prefix '/opt/local') the python extension fail with the ominous 'fantastic lxml wrapper for libxml' story :(
Will try again tomorrow, but might need some help as well on how to create 'portable' python module packages...
sorry, ~suv