Hi Antonio,Gert is correct, our compatibility layer is a set of functions in
wolfSSL which emulate the OpenSSL API. These functions are then macro defined
to have the same names as the OpenSSL functions. The configure script needs to
know where the wolfSSL headers are and that it should link against the wolfSSL
binary, not OpenSSL. This is the reason for the configure script
changes.Sincerely Juliusz
-------- Original message --------From: Antonio Quartulli <a...@unstable.cc>
Date: 09/02/2020 10:52 (GMT+01:00) To: Gert Doering <g...@greenie.muc.de> Cc:
Juliusz Sosinowicz <juli...@wolfssl.com>, openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] [PATCH] Support for wolfSSL with OpenVPN master
branch Hi,On 09/02/2020 10:50, Gert Doering wrote:> Hi,> > On Sun, Feb 09,
2020 at 10:44:48AM +0100, Antonio Quartulli wrote:>> if wolfssl support is
being introduced by means of the openssl>> compatibility layer, why do people
need to configure OpenVPN with>> "./configure --with-crypto-library=wolfssl",
rather than just using>> openssl and specifying a different path for
headers/libraries?>>>> Isn't the compat layer in wolfssl operating as a drop-in
replacement for>> openssl?> > This question has been asked before and answered
:-) - most of the> compat functions seem to be implemented as macros, which our
configure> will not find. So, configure needs to explicitely define what is
there> and what not.> > I do not like the extra include very much, but that
seems to be hard > to avoid with the current WolfSSL header file setup.> ouch,
thanks for the reminder :-)-- Antonio Quartulli
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
