Context: https://github.com/llvm/llvm-project/issues/63890
These builtin headers are required to exist alongside clang-tidy for it to work. Specifically, the tool looks for headers relatively in ../lib/clang/{major version}/include.
Differential D156433
[bazel] Include builtin headers with clang-tidy jathu on Jul 27 2023, 7:11 AM. Authored by
Details
Context: https://github.com/llvm/llvm-project/issues/63890 These builtin headers are required to exist alongside clang-tidy for it to work. Specifically, the tool looks for headers relatively in ../lib/clang/{major version}/include.
Diff Detail
Event TimelineComment Actions I like this change. If something like this also works for the clang target and maybe a few others it would relieve downstream users from implementing logic around this resource path. (E.g. it could potentially reduce some of the hackiness in https://github.com/eomii/rules_ll/blob/37b5721a8083d36332eaca1f62fcc43b8aba7bd1/ll/args.bzl#L9-L47).
Comment Actions bump for anyone in the @bazel_build group. cc @goncharov @gchatelet @hokein (based on git history for clang-tidy) This will unblock clang-tidy builds and allow it to be used out of the box This comment was removed by jathu. Comment Actions Closing this diff to attempt to get another fresh pair of eyes on this change: D158942 |
This seems to better fit into the clang directory in the overlay so that targets can consume //clang:builtin_headers.