jj/buck/third-party/bssl/README.md

## BoringSSL Notes

When you update this package, including the git commit and archive hash, make
sure you also re-download the proper `BUILD.generated.bzl` file, which is
produced automatically by a bot in the upstream `master-with-bazel` branch:

- https://github.com/google/boringssl/tree/master-with-bazel

```
curl -Lo \
    buck/third-party/cxx/bssl/BUILD.generated.bzl \
    https://raw.githubusercontent.com/google/boringssl/.../BUILD.generated.bzl
```
buck: build boringssl `libgit2` requires `libssh2`, which in turn requires `openssl-sys`. OpenSSL is notoriously hard to vendor for a number of reasons including its build system. In contrast, while BoringSSL does not make compatibility guarantees, it is easy to vendor and is designed to be used with Bazel. The goal is that we can substitute BoringSSL for OpenSSL in `openssl-sys` as the underlying library, and `libssh2` will still work. Signed-off-by: Austin Seipp <aseipp@pobox.com> 2024-05-10 22:47:13 +00:00			`## BoringSSL Notes`

			`When you update this package, including the git commit and archive hash, make`
			sure you also re-download the proper `BUILD.generated.bzl` file, which is
			produced automatically by a bot in the upstream `master-with-bazel` branch:

			`- https://github.com/google/boringssl/tree/master-with-bazel`

			```
			`curl -Lo \`
			`buck/third-party/cxx/bssl/BUILD.generated.bzl \`
			`https://raw.githubusercontent.com/google/boringssl/.../BUILD.generated.bzl`
			```