-
Notifications
You must be signed in to change notification settings - Fork 75
Open
Description
To me, the most important thing isn't how long a full build takes, but rather an incremental build. For example, over the course of the day, as I switch branches, rebase, bisect, etc. I'd love to be able to see stats representing that.
My mental model of ClangBuildAnalyzer is that --start puts a file in the build dir, and that --stop then searches the build dir for all .cpp.json files newer than the "start" file, and analyzes them. Likewise --all just looks at all of them.
To get what I want, I think I'd need to run a script every time I build that...
- Searches the build dir for
.cpp.jsonfiles and - copies them to an output folder as
$(sha1sum foo.cpp.json).cpp.json.
So for example, if I rebuiltfoo.cppthree times, I would have three separate.cpp.jsonfiles, once for each build.
Then I'd runCalngBuildAnalyzeron that output folder to find out where my time waiting for builds has actually gone over the course of the day.
Should that work? Is there interest in this?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels