Ok, I've managed to fix this issue in a slightly different way. I discovered that the dylib files my installation was searching for were not packaged with the plugin code due to the fact that they were in a hidden directory and hidden directories were not included in my git commits.
At the end of the day, it was as simple as copy and committing ALL site-package contents! On Monday, October 31, 2016 at 11:54:04 AM UTC-4, Evan Molinelli wrote: > > Hi all, > > I'm trying to use a 3rd party library (in this case Pillow) which has > binary dependencies (libjpg -version 9). I can easily get this working on > MY machine by (1) brew install libjpg, (2) pip install Pillow, and (3) > adding the Pillow site-packages directory to maya's python path. > > The issue I'm having is how to package my python plugin with its Pillow > dependency. I've built the Pillow package for mac os and windows x64 (the > machines I know I need to support) and on initialization I add the relevant > folders to the path and that all seems to work. > > The problem is that I need to include machine dependent builds of the > libjpg library and then link them on initialization. I've found this > reference > > https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/2016/ENU/Maya-SDK/files/GUID-E7B113F2-5AFD-4C05-A747-298C06586447-htm.html > > but* I am unsure how and where to actually DO the linking for macs*. > Something like using "install_name_tool" maybe? > > Any assistance would be greatly appreciated. > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/aaa06796-fd30-4211-95c4-7cdd325d1146%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
