2010-12-10 22:17:57 +03:00
|
|
|
/**
|
|
|
|
|
|
|
|
@page libssh_linking The Linking HowTo
|
|
|
|
|
|
|
|
@section dynamic Dynamic Linking
|
|
|
|
|
|
|
|
On UNIX and Windows systems its the same, you need at least the libssh.h
|
|
|
|
header file and the libssh shared library.
|
|
|
|
|
|
|
|
@section static Static Linking
|
|
|
|
|
2010-12-21 17:03:13 +03:00
|
|
|
@warning <b>The libssh library is licensed under the LGPL! Make sure you
|
2010-12-10 22:17:57 +03:00
|
|
|
understand what this means to your codebase if you want to distribute
|
2010-12-21 17:03:13 +03:00
|
|
|
binaries and link statically against LGPL code!</b>
|
2010-12-10 22:17:57 +03:00
|
|
|
|
|
|
|
On UNIX systems linking against the static version of the library is the
|
|
|
|
same as linking against the shared library. Both have the same name. Some
|
|
|
|
build system require to use the full path to the static library.
|
|
|
|
|
2013-08-01 16:07:36 +04:00
|
|
|
To be able to compile the application you're developing you need to either pass
|
|
|
|
LIBSSH_STATIC as a define in the compiler command line or define it before you
|
|
|
|
include libssh.h. This is required cause the dynamic library needs to specify
|
|
|
|
the dllimport attribute.
|
|
|
|
|
|
|
|
@code
|
|
|
|
#define LIBSSH_STATIC 1
|
|
|
|
#include <libssh/libssh.h>
|
|
|
|
@endcode
|
2010-12-10 22:17:57 +03:00
|
|
|
|
2019-03-13 12:36:03 +03:00
|
|
|
If you're are statically linking with OpenSSL, read the "Linking your
|
2020-03-27 14:06:06 +03:00
|
|
|
application" section in the NOTES.[OS] in the OpenSSL source tree!
|
2019-03-13 12:36:03 +03:00
|
|
|
|
2010-12-10 22:17:57 +03:00
|
|
|
*/
|