dylib is the OSX equivalent of Linux .so, so nothing wrong here.
Looking at the ffi documentation it seems that libraries are looked into a
list of paths reported by (get-lib-search-dirs)
See
https://docs.racket-lang.org/raco/dirs.html#%28def._%28%28lib._setup%2Fdirs..rkt%29._get-lib-search-dirs%29%29
>> i guess the problem is that your libsodium installation dir is not
listed there

To change this search list you should modify the ´lib-search-dirs
configuration as described here:
https://docs.racket-lang.org/raco/config-file.html

HTH


Le jeu. 13 déc. 2018 à 23:46, David Storrs <[email protected]> a
écrit :

>
> https://docs.racket-lang.org/crypto/factory.html#%28def._%28%28lib._crypto%2Fsodium..rkt%29._sodium-factory%29%29
>
> "Factory for Sodium <https://download.libsodium.org/doc/> (aka libsodium).
> This factory does not provide the high-level Sodium APIs; it only
> provides access to some of the low-level primitives. The
> libsodium.so.{23,18} library is required."
>
> When compiling libsodium on OSX 10.11 I get:
>
> /usr/local/lib/libsodium.23.dylib
> /usr/local/lib/libsodium.a
> /usr/local/lib/libsodium.dylib -> libsodium.23.dylib
> /usr/local/lib/libsodium.la
>
> Unsurprisingly, the Racket crypto library's libsodium-factory is
> unavailable, since there's no libsodium.so available.  I get the same
> .dylib and .a files if I install via homebrew, except off in
> /usr/local/Cellar instead of a standard lib directory.
>
> I've got the library, so is there a way to make crypto notice that fact?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to