Opened 14 years ago
Last modified 14 years ago
#654 new enhancement
Add c:gcclint recipe command
Reported by: | hodgestar | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 0.7 |
Component: | Recipe commands | Version: | 0.6b3 |
Keywords: | c gcc lint | Cc: | |
Operating System: |
Description
GCC produces warnings while compiling. It would be useful to provide support for parsing these and converting them to Bitten report via a recipe command.
Attachments (1)
Change History (2)
Changed 14 years ago by hodgestar
comment:1 Changed 14 years ago by hodgestar
Discussion of parsing gcc warnings into a lint report started on the mailing list (https://groups.google.com/d/topic/bitten/c3TJm6rcWUA/discussion) when Stefan Rupert posted an Awk script to perform the task. W Martin Borgert converted the Awk script to a Python one which Stefan then extended. I've attached the final script to this ticket for reference.
The chief difficulty in converting this to a Bitten recipe command is probably how to capture standard output from gcc (or otherwise get at the GCC warnings). One possibility is modifying c:make to perform this or to tee standard to another file. There may be better approaches.
Script for parsing gcc output into a Bitten lint report.