2021-04-28 04:57 AM
I'm running PC-Lint as an external tool with the results going an output console. I'd like to be able to double click on a PC-Lint error message in the console and have the appropriate source file / line displayed as per compiler errors. I have PC-Lint error messages formatted the same as complier errors but the IDE ignores double clicks on these messages.
Is there any way to configure CubeIDE to get the desired behaviour ?
Solved! Go to Solution.
2021-05-05 04:42 AM
Hello!
This isn't really my area of expertise so if anyone in the community knows more about this feel free to answer.
I believe there are some plugins available for purchase that might work, but I'm not 100% sure about that.
Another "dirty hack" you could use is to start lint in conjunction with the build process. The output from lint would then be displayed in the "Build console" and it should be able to handle the the double click linking that you mentioned.
Or possibly start lint as a pre-build step or create a build configuration that launches lint instead of make.
I asked one of the developers that mentioned that he did something like what I link here. (External link to dzone.com)
2021-05-05 04:42 AM
Hello!
This isn't really my area of expertise so if anyone in the community knows more about this feel free to answer.
I believe there are some plugins available for purchase that might work, but I'm not 100% sure about that.
Another "dirty hack" you could use is to start lint in conjunction with the build process. The output from lint would then be displayed in the "Build console" and it should be able to handle the the double click linking that you mentioned.
Or possibly start lint as a pre-build step or create a build configuration that launches lint instead of make.
I asked one of the developers that mentioned that he did something like what I link here. (External link to dzone.com)
2021-05-05 05:25 AM
Markus
That's perfect! Actually just putting Lint as a pre-build step redirects Lint messages to the build console where I can double click to see the offending source line. Just what I needed.
Many thanks
Dave