Bug 512824 - Add option to ignore errors warnings from file or directory
Summary: Add option to ignore errors warnings from file or directory
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-codan (show other bugs)
Version: 9.2.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CDT Codan Inbox CLA
QA Contact: Elena Laskavaia CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-28 10:58 EST by Yan Pas CLA
Modified: 2017-03-10 10:28 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yan Pas CLA 2017-02-28 10:58:34 EST 
I have some cpp files in my project which are not included in build and I don't want them to generate errors. Now each time I open them to view I see tons of errors.
Comment 1 Elena Laskavaia CLA 2017-02-28 11:30:12 EST 
In project preferences, C/C++->General->Code Analysis
Click on error that shows up, click Customize switch to Scope tab
and your your files to exclusion filter. Currently there is global
filter for all errors, it on per error base.
Comment 2 Nathan Ridge CLA 2017-02-28 16:30:06 EST 
(In reply to Elena Laskavaia from comment #1)
> Currently there is global
> filter for all errors, it on per error base.

Did you mean to say currently there is *no* global filter for all errors?
Comment 3 Elena Laskavaia CLA 2017-03-01 18:04:09 EST 
(In reply to Nathan Ridge from comment #2)
> (In reply to Elena Laskavaia from comment #1)
> > Currently there is global
> > filter for all errors, it on per error base.
> 
> Did you mean to say currently there is *no* global filter for all errors?

Yes I missed the essential word as usual. No global filter.
Comment 4 Nathan Ridge CLA 2017-03-09 23:51:54 EST 
(In reply to Elena Laskavaia from comment #3)
> > Did you mean to say currently there is *no* global filter for all errors?
> 
> Yes I missed the essential word as usual. No global filter.

Thanks for clarifying.

Should we close this bug, or keep it open to track the addition of such a global filter?
Comment 5 Yan Pas CLA 2017-03-10 06:12:16 EST 
I don't think it should be closed. the same feature was requested for JDT (https://bugs.eclipse.org/bugs/show_bug.cgi?id=220928 40 subscribers!) and PHP (https://bugs.eclipse.org/bugs/show_bug.cgi?id=286397)
Comment 6 Nathan Ridge CLA 2017-03-10 10:28:10 EST 
Another approach might be to automatically disable code analysis in files that are not included in the build, or at least have an option to do so.