On Sunday, March 19, 2017 15:09:59 Tomasz Kłoczko wrote: > gcc can now load some extensions as DSOs and maybe it would be possible to > use this entry point to start thinking about develop extension which would > allow store formated data about types and locations of warning in some text > file per package which will be easier to parse and process. Parsing raw gcc > stderr output may be not so useful in such case. You can use 'csmock -t gcc' to get the list of warnings in a machine-readable format fully automatically for any SRPM without developing anything. > Even without above raw build logs preserved on koji enriched but full > warnings verbosity has some very big potential. I am not sure what you mean by "full warnings verbosity" but csmock allows you to transparently add custom compiler flags without the need to change anything in the build root or the packages being scanned. Kamil > kloczek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
