Update fuzzer documentation.
Change-Id: Id9dbaf42881a3ed3f377142b116151aebfd21192
Bug: None
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/368020
Commit-Queue: Jeremy Leconte <jleconte@webrtc.org>
Reviewed-by: Björn Terelius <terelius@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#43388}
diff --git a/docs/native-code/development/fuzzers/README.md b/docs/native-code/development/fuzzers/README.md
index cac77cd..b323756 100644
--- a/docs/native-code/development/fuzzers/README.md
+++ b/docs/native-code/development/fuzzers/README.md
@@ -4,6 +4,12 @@
WebRTC currently uses libfuzzer for fuzz testing however FuzzTest is a new approach which we have not yet looked into but we will in the future.
Before continuing, read the [libfuzzer][libfuzzer-getting-started] and [FuzzTest][fuzztest-getting-started] getting started docs to get familar.
+You will also need to download libfuzzer specific libraries, which are not downloaded by default. The easiest way to do this is to set the `checkout_fuzzer` custom variable in your .gclient file then run gclient runhooks.
+```
+ "custom_vars": {
+ "checkout_fuzzer": True,
+ },
+```
## Compiling locally
To build the fuzzers residing in the [test/fuzzers][fuzzers] directory, use
