Am 09.02.20 um 12:08 schrieb Juliusz Sosinowicz: > 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.
But OpenSSL also its opensslconf.h header and does not force you to important into each file it uses. I find that argument very weak. If it is something that is essential for your compat layer then you should probably include it in the top of each compatibility header. Arne
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
