Re: [Pharo-users] uFFI: Debugging "External module not found" Error

[Todd Blanchard via Pharo-users]

--- Begin Message ---

This is the most annoying thing about UFFI - the library search seems to opaque 
and I don't understand how it works.

So far I am finding best practice is to find the library yourself and then 
provide the exact file path you want.  

That way, you can actually prompt the user to find it if you don't and they get 
a decent experience.

> On Dec 3, 2019, at 11:34 AM, Sean P. DeNigris <s...@clipperadams.com> wrote:
> 
> Alistair Grant wrote
>> The same message is returned whether the module itself isn't found, or
>> if one of its dependencies can't be found.
> 
> Good to know. I wonder if we can't provide more detailed error messages
> here...
> 
> 
> Alistair Grant wrote
>> On linux you can check dependencies with `ldd file.so`, I don't know
>> what the Mac equivalent is.
> 
> Apparently, it's `otool -L whatever.dylib`, which returns:
>       @rpath/libvlc.dylib (compatibility version 12.0.0, current version 
> 12.0.0)
>       @rpath/libvlccore.dylib (compatibility version 10.0.0, current version
> 10.0.0)
>       /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
> 1252.50.4)
>       /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version
> 7.0.0)
> 
> 
> Still investigating...
> 
> 
> 
> -----
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 

--- End Message ---