add output_dir feature - #210
Conversation
|
Please review this pr :) |
|
@ilev4ik please don't mention people who don't even have the permissions to merge your PR (i.e. me, probably some others). FYI I suspect there's a chance this project will no longer be maintained now that Hedron Vision was acquired, though I have no inside information. |
|
@garymm how can I check if you have a permission or not? I relied on autocomplete when mentioning. It seems it was a mistake My apologises for inconvenience |
…itten New macro/rule parameter `output_dir` (default empty == workspace root, matching the historical behaviour). When set, both the pre-write unlink and the open() target are rerouted to `<output_dir>/compile_commands.json`. Backport of hedronvision#210 (ilev4ik).
|
Hi — since upstream has been quiet for a while, the fork at https://github.com/helly25/bazel-compile-commands-extractor has picked up this change as part of a viability sweep. Backported (with attribution preserved in the commit message) in helly25#13. Thanks for the original patch. |
3 participants
This pull request is about to provide a support of writing out compile_commands.json relatively to workspace root to provide each project means of customizing their .clangd.
By default compile-commands-extractor's refresh_compile_command produces its output into bazel-workspace root. But our monorepository is single-rooted workspace and has many subprojects as children folders. Multiple projects are maintained by one team of developers, but a single project may have its own clangd configuration.
I didn't find any customization attribute of bazel target so created this PR. If there exist any please let me know. TY
@cpsauer it would be great if you find some time to review PR :)
Closes #217