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.
I have a project that relies on the some external sources and I would prefer not to change them. The problem is that a lot of warnings are generated from these sources and it also slows down the whole process of running the analyzer on the code.
All these source files to be ignored are in the same directory so it would be convenient to able to flag the directory as a no go place for the analyzer.
Convenient yes, but possible?
See my answer here. You can add a compile flag to the files and static analyzer will ignore them.
You can mass add flags by multi-selecting files, pressing enter, entering the flags, and pressing enter again. If the third party code has been written with the proper name spacing, you should be able to use the filter to only show the files in those directories.