I'd like to help out more, but at this point, I don't have the time for the due diligence required for such an investigation. I also think we are getting sidetracked. The problem today isn't with any of the tools that PyInstaller is using.
Going back to the original issue for PySide, GDCM, etc, otool reports the dependency libraries just fine. It's PyInstaller that's improperly filtering out libraries in /usr/lib and /usr/local/lib. That would still be a problem if PyInstaller switches to macholib. So, my opinion of what really needs to be changed is how PyInstaller filters the dependency libraries. Cheers Mike > Could you please investigate what macholib can be used in pyinstaller > for? > > We already know that it could replace calling the otool (similar to ldd > on linux). Could it be use for anything else? -- 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.
