Community
Participate
Working Groups
Using the newly added "Test Plugin RegexErrorParser", I've added my own regexfilter to match the compiler error and warning output. Given the following compiler warning outout with regex filter, it works fine: Regex: Severity: Warning Pattern: (.*)\((\d+)\): warning: (.*) File: $1 Line: $2 Description: $3 Compiler warning output: C:/MyFolder/Subfolder/Animation.inl(27): warning: empty body in an else-statement -- However, if I want to "remap" the filepath, say from /Subfolder+, the File field won't translate this to what c:/Otherfolder/$1 should result in. Regex: Severity: Warning Pattern: (.*)/Myfolder/(.*)\((\d+)\): warning: (.*) File: C:/OtherFolder/$2 Line: $3 Description: $4 The file should result in: C:/OtherFolder/Subfolder/Animation.inl but this don't seem to work. Needless to say, this is an brute example. I whish to replace the mapping with a variable, say PWD or alike in the end.. Thanks, Andreas
> Compiler warning output: > C:/MyFolder/Subfolder/Animation.inl(27): warning: empty body in an else-statement You got "MyFolder" in your output > Pattern: (.*)/Myfolder/(.*)\((\d+)\): warning: (.*) but you placed "Myfolder" in the pattern. It won't match because of lowercase "f".
And should not source lookup mapping be used for that instead?
What source lookup mapping?
(In reply to comment #1) > > Compiler warning output: > > C:/MyFolder/Subfolder/Animation.inl(27): warning: empty body in an else-statement > You got "MyFolder" in your output > > Pattern: (.*)/Myfolder/(.*)\((\d+)\): warning: (.*) > but you placed "Myfolder" in the pattern. It won't match because of lowercase > "f". Sorry for the typo, but it is in fact just a typo. In the real case, the casing is correct. PS: I'm also interested in what Alena means with source-mapping..
(In reply to comment #4) > (In reply to comment #1) > Sorry for the typo, but it is in fact just a typo. In the real case, the casing > is correct. I tested your patterns and it works fine for me. Note that your file has to be in a eclipse workspace in open project for this to work. Do you get any problem marker at all? If so, what you get in Resource, Path, and Location columns? > PS: I'm also interested in what Alena means with source-mapping.. She meant "Common Source Lookup Path" in Debug in preferences but it is not available for error parsers. There is also bug 295627.
Andrew, I didn't realize the source have to be in a eclipse workspace in open project for this to work. That fixed it, sorry for the invoncenience and thank you for your response :) /Andreas
