See branch: rosuav/curve_crypto_guard
Is there a simpler way to cope with crypto absences than all the
#if'ing everywhere? It's easy to create a Pike that won't build on
systems that lack one or other.
ChrisA
See branch: rosuav/curve_crypto_guard
Merged, thanks.
Separating out thing with different dependencies into different files
would be one way, but it would still be difficult to do. You could
possibly reuse the compat resolver to prevent certain things from
loading, so you could verify that common variations still work.
