I filed 24011 to have this fixed. I'm using the GCC 4 parser.
On Tue, Jul 29, 2014 at 5:04 PM, Ulli Hafner
wrote:
> This depends on the parser. Most of the parsers create files with absolute
> filenames. If the parser produces relative paths then the absolute paths
> are determined after the fi
This depends on the parser. Most of the parsers create files with absolute
filenames. If the parser produces relative paths then the absolute paths are
determined after the filter operation.
But it should be possible to move the filtering after the expansion. Please
file a new feature request i
It seems that the problem is that the filter is not done on the absolute
path to the file, but rather the filename fragment that shows up in the
warning. This makes it very difficult to ignore all warnings for a given
directory. I need to list each file in the directory explicitly.
On Mon, Jul 28
I see that under the advanced section of the compiler warnings module there
is an option to ignore files based on their absolute file path. Does this
work to filter warnings found in the console output or only when scanning
files?
I have a directory at the top of my workspace named "log4cxx/source
