Introduction of --with-libtls etc.
robert-scheck opened this issue · comments
When crafting rpki-client/rpki-client-container@99690d3, I had to learn that Alpine's libtls-standalone-dev package doesn't put tls.h onto a standard path. Thus I would like to raise the idea for --with-libtls etc., that – like for OpenSSL – a pkg-config pkg-name (or other individual build-time paths) can be passed, too.
Please check out 0fd7b2b, this should implement what you want.
Yes, mostly, but with --with-libtls=libtls-standalone on Alpine Linux, I somehow get this:
checking tls.h usability... yes
checking tls.h presence... no
checking for tls.h... yes
configure: WARNING: tls.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: tls.h: proceeding with the compiler's result
checking for library containing tls_read... -ltls-standalone
checking for tls_default_ca_cert_file... yes
checking for tls_config_set_ca_mem... yes
Merged