pw_tls_client_mbedtls: Initial commit
Add docs and some placeholder data strucutre types to be implemented
later.
Bug: 398
Change-Id: Ib6b1f2cc7ee51218e174f6b645d983ed551d87c7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/50460
Commit-Queue: Yecheng Zhao <zyecheng@google.com>
Reviewed-by: Ali Zhang <alizhang@google.com>
diff --git a/pw_tls_client/docs.rst b/pw_tls_client/docs.rst
index 348ad44..5adfdba 100644
--- a/pw_tls_client/docs.rst
+++ b/pw_tls_client/docs.rst
@@ -60,7 +60,10 @@
1. Choose a ``pw_tls_client`` backend, or write one yourself.
2. If using GN build, Specify the ``pw_tls_client_BACKEND`` GN build arg to
- point the library that provides a ``pw_tls_client`` backend.
+ point the library that provides a ``pw_tls_client`` backend. To use the
+ MbedTLS backend, set variable ``pw_tls_client_BACKEND`` to
+ ``//pw_tls_client_mbedtls``. To use the BoringSSL backend, set it to
+ ``//pw_tls_client_boringssl``.
3. Provide a `pw_tls_client:entropy` backend. If using GN build, specify the
backend with variable ``pw_tls_client_ENTROPY_BACKEND``.