Originally published on 2011-12-15 03:15
How do I analyse my software when it's being built with BitBake? I'm trying to analyse a version of Linux kernel and the end result is that Coverity doesn't see any compilation commands and therefore doesn't analyse any files.
I understood that it should be possible to use Coverity with BitBake.
Originally published on 2011-12-23 16:03
It's definitely possible; I implemented it a few years ago in 3.x/4.x, for a previous employer, and it went remarkably smoothly, especially compared to our earlier build system. Details were confidential at the time, though the product is now open source, so I may be able to provide them. But first I'd suggest checking your compiler configuration, which may be more relevant than the build system--also check if you're doing anything nonstandard, like distributed builds.
Originally published on 2011-12-28 13:17
Tell BitBake to whitelist the following environment variables:
There may be a few others - best way to tell may be to run your build with cov-build --debug flag and look for COVERITY_xxx environment variables in the build-log.txt file.
Originally published on 2012-01-09 00:35
The list I got was
so it looks like I need to add a few more...