Willy, > > Fred told me that he manages to build it using the fork of openssl that > contains the proper stuff. Hopefully it should get merged soon. But with > BoringSSL the problem is that something that works on monday suddenly > fails to build on tuesday and there's no stable branch so you're just > forced to change your API to adapt to it on the fly. I don't want to > blame them too much because they always warned against this. It's been > convenient to start on QUIC but as soon as we can avoid this pain it > will be better to get rid of it.
I totally agree, the only reason I tried to build with BoringSSL is its QUIC support. If QUIC can be done using a library with stable API then there's no need to endure the pain of keeping up with BoringSSL changes. Thanks, Bob
