title: How do I get SonarQube Scanner to analyze C and C++ code?
body: <p>I am running the community edition of SonarQube 7.1 on RHEL 7.x.  When I run sonar-scanner -X, I see the output on the backend like this:</p>
  
  <pre><code>hello.py indexed with language 'py'
  hello.java indexed with language 'java'
  hello.cpp indexed with language 'null'
  hello.c indexed with language 'null'
  </code></pre>
  
  <p>I expected to see "indexed with language cpp" and "indexed with language c".  </p>
  
  <p>When I go to the web UI, see the hello.py and hello.java in the project directory.  But I see no reference to the .cpp or .c code.  I expect to see the .c and .cpp files in the web UI.  This has never worked, so let me give some background on what I did.</p>
  
  <p>To install the plugin for the .cpp and .c code, I downloaded a .zip file with the highest version number.  I initially tried to find it on the local SonarQube installation, but the URL "<a href="http://localhost:9000/static/cpp/build-wrapper-linux-x86.zip" rel="nofollow noreferrer">http://localhost:9000/static/cpp/build-wrapper-linux-x86.zip</a>" (and its derivatives for my own deployment) did not work for me.  As a side note, I am curious if there are alternative paths and why this path would lead to 404 or "No page can be displayed" messages in my web browser.</p>
  
  <p>After I unzipped the plugin for C++ and C, I ran (from the command prompt): build-wrapper-linux-x86-64 --out-dir bw_output make</p>
  
  <p>I also ran (from the command prompt): build-wrapper-linux-x86-64 --out-dir bw_output make sonar-scanner</p>
  
  <p>Both ran without errors.  It appears that SonarQube is not analyzing .c or .cpp source code.  I base this off two things.  One, the lack of output in the web UI when other files are analyzed in the same directory. Two, the output on the backend referring to language 'null' for .c and .cpp files.  What am I doing wrong in configuring SonarQube to analyze C and C++ code?</p>