Fix include checking for boringssl_fuzzer target
Ideally we wouldn't have a separate boringssl_fuzzer target at all
(crbug.com/42290128), but while we do, keep them in sync.
The setup in GN is that we keep internal headers unexported (missing a
"public" field means all headers are implicitly exported), but mark all
targets in the same package as "friend" because BoringSSL targets all
include each others private headers.
Fixed: 40938301
Change-Id: I9aa6f108bbcad60ab5f5a17013ac431acef34d9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5803342
Auto-Submit: David Benjamin <davidben@chromium.org>
Commit-Queue: Bob Beck <bbe@chromium.org>
Reviewed-by: Bob Beck <bbe@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1348906}
NOKEYCHECK=True
GitOrigin-RevId: 699ecfa46d32ef3b92bd9a168e8a61031172646e
1 file changed
