Open abiggerhammer opened 10 years ago
Hi @abiggerhammer,
sorry for the slow response. We made some changes to this library to embed all the necessary tools and be able to run the tests on Travis.
To move forward on this, we would basically need an analyzer for each of the tools which you would like to run on the code and parse their output so that it can be further processed by Scrutinizer.
If you do not mind writing some PHP code, it should be mostly copy/paste with some adjustments to the configuration/parsing algorithm. For example as a starting point the JSHint analyzer is relative simple: https://github.com/scrutinizer-ci/scrutinizer/blob/master/src/Scrutinizer/Analyzer/Javascript/JsHintAnalyzer.php
:+1: for c/c++
I will probably have time to poke at this sometime this week and/or weekend.
Is there any update on this issue? Will you guys support some basic C/C++ analysis/verification?
I would be also interested on some sort of C/C++ support in scrutinizer
I would also love to see some basic c/c++ support in scrutiniser :-)
I maintain a C library for which it would be amazing to be able to run tools such as memcheck, DRD and other tools from the Valgrind suite as part of our build automation process. What would need to be done to provide these sorts of tools in scrutinizer-ci?