Here is my otool -L output: @rpath/libjpeg.7.dylib (compatibility version 8.0.0, current version 8.0.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0)
I have added those files specifically to the .spec file's a.binaries. I'm not sure what @rpath is supposed to be or if I can change it to something else. Any ideas on that? My python install as well as PIL are from Enthought Python 7.2. I'm using Enthought Python because I was having a hard time getting wxPython and H5py working together properly on the Mac. On Tuesday, June 19, 2012 12:56:12 AM UTC-7, Martin Z wrote: > > Hi, > > on IRC you wrote: > > I've gone through and explicitly included anything PIL._imaging > seems to need. > pyinstaller.py does seem to have a problem finding any .so files > that start with @rpath > > How did you install PIL? > > It seems like your PIL._imaging.so has some dependencies starting with > @rpath. > What is your output of command > > otool -L PIL._imaging.so > > My is: > > PIL/_imaging.so: > /opt/local/lib/libjpeg.8.dylib (compatibility version 12.0.0, current > version 12.0.0) > /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current > version 1.2.6) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 159.1.0) > > PyInstaller is able to handle only @lib_path and @executable_path. > > Question is: What path prefix to use instead of @rpath? > > In other words, where should Pyinstaller look for missing .so/.dylib > files? PyInstaller needs to know the real path, not @rpath. > > mmiscavage píše v Po 18. 06. 2012 v 11:29 -0700: > > I am running on Mac osX 10.7.4 using the > > pyinstaller-pyinstaller-2145d84.tar.gz. I was able to get this project > > working on Windows 7 but cannot get past this error on Mac. I am able > > to 'from PIL import _imaging' from the Python interactive console. The > > pyinstaller.py successfully finds the _imaging.so and puts it in the > > dist folder with all other lib files. Is this something I should be > > looking to make a hook for ? Or is something else wrong? Any help or > > nudge in the right direction would be appreciated. > > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To view this discussion on the web visit https://groups.google.com/d/msg/pyinstaller/-/FNYm52Wx58sJ. 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.
