Simon Josefsson <[email protected]> writes: > Thanks, I'm a bit surprised by these changes - did you test that it is > possible to still build things without linking to OpenSSL? That is one > of the main reasons for the gc* modules, to have a "generic crypto" API > that is not tied to any particular underlying library. So if anything > there should be a lib/gc-openssl.c that contain the gc->openssl mappings > needed. It should be possible to use all gc* modules with either > OpenSSL, libgcrypt or native gnulib implementations (although there > could be minor deviations from this general policy if some algorithm is > not implemented in one "backend").
Yep, if you use '--with-openssl=no', for example, the gnulib implementation is used. And $(LIB_CRYPTO) will expand to nothing. I think that is the behavior you expect. But let me know if not. Collin
