Lines Matching +full:application +full:- +full:notes

1 Notes for UNIX-like platforms
5  please see the [Notes for Windows platforms](NOTES-WINDOWS.md).
8  ---------------------------------------------------------------
15  linker flags directly, while others take them in `-Wl,` form.  You need
19  Shared libraries and installation in non-default locations
20  ----------------------------------------------------------
24  libraries are installed in non-default locations, dynamically linked
28  For OpenSSL's application (the `openssl` command), our configuration
43     -Wl,-rpath,/whatever/path   # Linux, *BSD, etc.
44     -R /whatever/path           # Solaris
45     -Wl,-R,/whatever/path       # AIX (-bsvr4 is passed internally)
46     -Wl,+b,/whatever/path       # HP-UX
47     -rpath /whatever/path       # Tru64, IRIX
51  with `-Wl,` are recognised as linker options.)
52  Please note that 'l' in '-Wl' is lowercase L and not 1.
61     $ ./Configure --prefix=/usr/local/ssl --openssldir=/usr/local/ssl \
62         '-Wl,-rpath,$(LIBRPATH)'
89     $ ./Configure --prefix=/usr/local/ssl --openssldir=/usr/local/ssl \
90         '-Wl,--enable-new-dtags,-rpath,$(LIBRPATH)'
97  Linking your application
98  ------------------------
100  Third-party applications dynamically linked with OpenSSL (or any other)
101  shared library face exactly the same problem with non-default locations.
103  on linking of the target application. "Might" means that under some
105  "naturally", i.e. with `-L/whatever/path -lssl -lcrypto`. But there are
107  when linking your application. Consult your system documentation and use
115  differently, add `_a` suffix to link with them, e.g. `-lcrypto_a`.