You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
apply_fixes can parse report files from a DWYU execution log
For large workspaces discovering the DWYU report files by crawling the bazel-out
directory can be quite slow due to an enormous amount of files and directories
being present.
To work around this, we enable the apply_fixes script to parse a log file
containing the command line output of executing the DWYU aspect. This execution
log is then parsed and the DWYU report paths deduced.
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -248,6 +248,10 @@ You can see the full command line interface and more information about the scrip
248
248
If the `apply_fixes` tool is not able to discover the report files, this can be caused by the `bazel-bin` convenience symlink at the workspace root not existing or not pointing to the output directory which was used by to generate the report files.
249
249
The tool offers options to control how the output directory is discovered.
250
250
251
+
Discovering the DWYU report files automatically can take a large amount of time if the `bazel-bin` directory is too large.
252
+
In such cases you can pipe the command line output of executing the DWYU aspect into a file and forward this file to the apply_fixes script via the `--dwyu-log-file` option.
253
+
The apply_fixes script will then deduce the DWYU report file locations without crawling though thw whole `bazel-bin` directory.
254
+
251
255
Unfortunately, the tool cannot promise perfect results due to various constraints:
252
256
253
257
- If alias targets are involved, this cannot be processed properly.
0 commit comments