clangToolingCore is linked into almost everything (incl. clang), but
not few tools need #include manipulation at this point. So pull this into a
separate library in Tooling.
Details
Details
- Reviewers
ilya-biryukov - Commits
- rG44564ac7eb4d: Reland "Move #include manipulation code to new lib/Tooling/Inclusions."
rG4f20e9de0a25: Reland "Move #include manipulation code to new lib/Tooling/Inclusions."
rGe0a3f5b1a965: Move #include manipulation code to new lib/Tooling/Inclusions.
rC333874: Reland "Move #include manipulation code to new lib/Tooling/Inclusions."
rL333874: Reland "Move #include manipulation code to new lib/Tooling/Inclusions."
rC333532: Reland "Move #include manipulation code to new lib/Tooling/Inclusions."
rL333532: Reland "Move #include manipulation code to new lib/Tooling/Inclusions."
rC332720: Move #include manipulation code to new lib/Tooling/Inclusions.
rL332720: Move #include manipulation code to new lib/Tooling/Inclusions.
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
LGTM with a minor naming suggestion.
include/clang/Format/Format.h | ||
---|---|---|
20 ↗ | (On Diff #147504) | Maybe Tooling/Includes? |
include/clang/Format/Format.h | ||
---|---|---|
20 ↗ | (On Diff #147504) | I decided to use Inclusions over Includes or Headers because those two can be confused with directories that contain headers for the library. |
Comment Actions
This was reverted in r332751 due to build bot failure with module config. I don't see how this failed as the directory setup is very similar to Tooling/Core/. Will investigate further next week.