67a9889ef7
The "share" directory holds platform-independent files, while "lib" holds platform-specific files. In principle, the "collects" directory belongs in "share", as does "doc". Those directories are put into "share" by a Unix-style install, but left at top level for an in-place install. Packages in installation scope are put in "share" instead of "lib", and the top-level Makefile puts development links in "share/devel-pkgs". The `configure' script now supports `--docdir' and `--collectsdir'. Changed the version to 5.90.0.1.
23 lines
712 B
Racket
23 lines
712 B
Racket
#lang racket/base
|
|
(require ffi/unsafe
|
|
racket/runtime-path
|
|
(for-syntax racket/base))
|
|
|
|
(provide libcrypto
|
|
libcrypto-load-fail-reason)
|
|
|
|
(define libcrypto-load-fail-reason #f)
|
|
|
|
;; We need to declare because they might be distributed with Racket,
|
|
;; in which case they should get bundled with stand-alone executables:
|
|
(define-runtime-path libcrypto-so
|
|
(case (system-type)
|
|
[(windows) '(so "libeay32")]
|
|
[else '(so "libcrypto")]))
|
|
|
|
(define libcrypto
|
|
(with-handlers ([exn:fail? (lambda (x)
|
|
(set! libcrypto-load-fail-reason (exn-message x))
|
|
#f)])
|
|
(ffi-lib libcrypto-so '("" "1.0.0" "1.0" "0.9.8b" "0.9.8" "0.9.7"))))
|