Message-ID: <1826169081.789666.1386581692410.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_789665_281592946.1386581692410" ------=_Part_789665_281592946.1386581692410 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can analyze your projects using the usual means (see this page for all available). All runners s= hould work. See below for details.
Analysis of a c++ project involves usually three steps:
There may be a Step '0' too: "use your build system to make a build= suitable for running the Step 1". This may be the case for collecting= coverage statistics when using gcc+gcov, for example.
For details how to invoke the tools and tie it all together see the = ;sample project.
There is a maven plugin which automates running of a sonar analysis on a= C++ project but requires a maven setup. Running a SonarQube analysis on ma= ven projects is quite simple and usually a matter of:
Start the analysis with
"mvn sonar:sonar" or&nb=
sp;"mvn sonar:sonar -Dsonar.phase=3Dcxx:addsource"
For details see the sample maven project.