Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It seems Bitbake build creates processes that print the actual build outputs to log files rather than standard output.
Is there a way to make them print to stdout? I need this to analyze a software with Coverity. Coverity captures the calls to the compiler from stdout to figure out which files to analyze and with what options they are built. With Bitbake it can’t see a single compile command…
Coverity Static Analysis does not depend on anything being output to "standard output" to work. The issue you are seeing with BitBake is caused by environment variables that SA relies on to capture calls to the compiler being wiped clean by BitBake.
In order to resolve the problem you need to white list variables SA uses with BitBake (likely by setting
BB_ENV_WHITELISTor equivalent appropriately).I think BitBake may have a way to preserve the entire environment (setting
BB_PRESERVE_ENV) however, I don’t know if that may impact your native build so I would hesitate to suggest it.