Digging in a little further and the omission of DYLD_LIBRARY_PATH from
the bootloader seems to be the cause of my headache.
ImageMagick looks for the decoders and filters on this path, and when
packaged, it can not find them even when I set DYLD_LIBRARY_PATH in the
start of my app.. Also looking at the dylib files, there are some links
that are changed to @loader_path, but some system files are left
pointing to the system path on my dev machine. I am assuming that in 1.5
the links that are left to the system path are found because of the
DYLD_LIBRARY_PATH setting.. Is there a workaround for this in 2.0?
something I need to do differently when packaging?
-Tim
On 8/10/12 10:39 AM, Concussion GFX - Tim wrote:
@loader_path seems to be the cause the my issues. I just noticed this
change:
" * (OSX) Bootloader does not use DYLD_LIBRARY_PATH on Mac OS X anymore.
@loader_path is used instead."
So cTypes is loading "libMagickWand.dylib" from the correct path, but
libMagickWand.dylib does not load from the temp dir. libclparser.dylib
should be loaded from the temp dir and not the system path.
File "/build/pyi.darwin/FrameThrower_OSX/out00-PYZ.pyz/ctypes", line
353, in __init__
OSError:
dlopen(/var/folders/lm/6dbp1cb91hj82pv_h1gncp_w0000gn/T/_MEI9Y3QrS/libMagickWand.dylib,
6): Library not loaded:
/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libclparser.dylib
Referenced from:
/var/folders/lm/6dbp1cb91hj82pv_h1gncp_w0000gn/T/_MEI9Y3QrS/libMagickWand.dylib
What needs to be done for libMagickWand.dylib to look in the correct dir?
Thanks
-Tim
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
