Code Analysis Runs On File Not Included In Build

Kier said:

Code analysis flags up a problem in a file that is not included in the build. Is that intentional

The default CCS behavior is to have CODAN disabled due to the propensity of false positives. However sometimes it gets enabled for a project. 

Kier said:

is there a way to configure CCS to analyse only relevant build files please?

CODAN settings can be set at the workspace and project level, not at an individual file level

https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#code-analysis

Thanks

ki

Ki said:

The default CCS behavior is to have CODAN disabled due to the propensity of false positives. However sometimes it gets enabled for a project. 

Thank you but this misses the point. Should a file excluded from the build be included in the code analysis? I would expect not, so the fact that it is suggests  a problem. If this is expected behaviour, what would be the rationale?

Ki said:

The default CCS behavior is to have CODAN disabled due to the propensity of false positives.

I couldn't find a global enable/disable control. Also if I create a new workspace and New project, code analysis is enabled by default since some of the items are selected:

How is CODAN globally disabled/enabled and how is it disabled by default please?

I think I found the answer to this question. I'm guessing that deselecting both items under Launching effectively disables CODAN.