Re: Add option to disable shared libs

> On 30 Oct 2017, at 03:03, Andreas Schneider 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

Re: setting up an environment for cross-compiling static libssh-projects

On Saturday, 28 October 2017 15:05:52 CET Daniel Brodt wrote: > Hi everybody, > I don't really know about windows cross compiling, but it seems to work just fine if you look at: https://build.opensuse.org/package/show/windows:mingw:win64/mingw64-libssh Also the Windows on KDE project

Re: Add option to disable shared libs

On Sunday, 29 October 2017 02:46:01 CET Tony Theodore wrote: > Hi, > > It’s sometimes useful to separate the build of static and shared libs, > the patch below is fairly straightforward but I’ve broken it in two as > I can’t the get re-indentation to display as a single hunk. Hi, we support to

Re: [PATCH 07/11] libcrypto: get compiling with BoringSSL

On Sunday, 10 September 2017 05:12:50 CET Jon Simons wrote: > With this change, libcrypto.c will compile with BoringSSL. To > get this working here's what I did: > > * Include the libcrypto-boringssl-compat shim header when building >with OPENSSL_IS_BORINGSSL. > > * Bring in a few more