You can analyze your projects using the usual means (see this page for all available). All runners should work. See below for details.
The usual setup
Analysis of a c++ project involves usually three steps:
- Run the tools (see ) which are of interest for you and store the results in a file somewhere underneath the root directory of your project. Its usually convenient to put this into the build system; a shell script may be a good choice, too.
- Provide a configuration using the file "sonar-project.properties". Set following properties, besides the standard ones:
- Use the SonarQube runner to start the analysis and feed the data into SonarQube.
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 maven projects is quite simple and usually a matter of:
- Getting and installing the cxx-maven-plugin (usage).
- Setting the language property and the source directory in your pom:
- Make sure your SonarQube server is running.
Start the analysis with
"mvn sonar:sonar" or "mvn sonar:sonar -Dsonar.phase=cxx:addsource"
For details see the sample maven project.