Merge "BPF: rename bpf_defaults to bpf_cc_defaults" into main am: d0ea163941
am: 482bad125d
Original change: https://android-review.googlesource.com/c/platform/build/soong/+/3268011 Change-Id: I550ac4386c056ef4ac04b73f25ecd05707b6f3c4 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
committed by
Automerger Merge Worker
commit
fed2df02fa
@@ -38,7 +38,7 @@ For example, in
|
||||
clang-tidy is enabled explicitly and with a different check list:
|
||||
```
|
||||
cc_defaults {
|
||||
name: "bpf_defaults",
|
||||
name: "bpf_cc_defaults",
|
||||
// snipped
|
||||
tidy: true,
|
||||
tidy_checks: [
|
||||
@@ -52,7 +52,7 @@ cc_defaults {
|
||||
}
|
||||
```
|
||||
That means in normal builds, even without `WITH_TIDY=1`,
|
||||
the modules that use `bpf_defaults` _should_ run clang-tidy
|
||||
the modules that use `bpf_cc_defaults` _should_ run clang-tidy
|
||||
over C/C++ source files with the given `tidy_checks`.
|
||||
|
||||
However since clang-tidy warnings and its runtime cost might
|
||||
|
Reference in New Issue
Block a user