Lines Matching refs:shared
140 you with a self-contained implementation in the form of a shared-library.
145 shared-libraries. It should be possible for hardware vendors to provide
146 their own shared-libraries to support arbitrary hardware to work with
166 implementation from a shared-library. To see these control commands,
172 shared-library that contains the ENGINE implementation, and "NO_VCHECK"
175 "ID" is probably only needed if a shared-library implements
184 the shared-library ENGINE implementation. If this command succeeds, the
186 that has been loaded from the shared-library. As such, any control
188 normal. For instance, if ENGINE "foo" is implemented in the shared-library
258 a shared-library that can be loaded by "dynamic" isn't automated in
260 Such a shared-library can either be built with any OpenSSL code it
262 if OpenSSL itself is built as a shared library. The instructions are
270 crypto/engine/ directory as a shared-library for use via the "dynamic"
290 4. Link "tmp_atalla.o" into a shared-library using the top-level
293 known well to anyone who has worked with shared-library portability
296 gcc -shared -o dyn_atalla.so tmp_atalla.o -L../.. -lcrypto
298 5. Test your shared library using "openssl engine" as explained in the
304 If the shared-library loads successfully, you will see both "-pre"
