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.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany [email protected]
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-devel
