[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Add option to disable shared libs
[Thread Prev] | [Thread Next]
- Subject: Re: Add option to disable shared libs
- From: Andreas Schneider <asn@xxxxxxxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Mon, 30 Oct 2017 08:20:01 +0100
- To: libssh@xxxxxxxxxx
On Monday, 30 October 2017 01:13:51 CET Tony Theodore wrote: > > On 30 Oct 2017, at 03:03, Andreas Schneider <asn@xxxxxxxxxxxxxx> wrote: > > > > we support to build libssh as a static library but we do not encourage it. > > I think you know what happens when you link your code with libssh > > statically. > What are the issues with static linking? I don’t use libssh myself, I just > packaged it for MXE (windows cross-compile)[1] and we separate static/shared > builds. It seems to work just fine. libssh is licensed under the LGPL. I suggest to read the sections about linking. Andreas -- Andreas Schneider GPG-ID: CC014E3D www.cryptomilk.org asn@xxxxxxxxxxxxxx
Add option to disable shared libs | Tony Theodore <tony.t@xxxxxx> |
Re: Add option to disable shared libs | Andreas Schneider <asn@xxxxxxxxxxxxxx> |
Re: Add option to disable shared libs | Tony Theodore <tony.t@xxxxxx> |