title: ndk-build can't find arm or mips headers
body: <p>When I try to build with Eclipse under Windows I have the following confusing output (extra paths shortened to '*'):</p>
  
  <pre><code>*\android-ndk-r9b-windows-x86_64\android-ndk-r9b\ndk-build.cmd 
  [x86] Compile        : P1 &lt;= CompilationUnitC.c
  [x86] Compile++      : P1 &lt;= CompilationUnitCPP.cpp
  [x86] SharedLibrary  : libP1.so
  [x86] Install        : libP1.so =&gt; libs/x86/libP1.so
  [armeabi] Compile thumb  : P1 &lt;= CompilationUnitC.c
  [armeabi] Compile++ thumb: P1 &lt;= CompilationUnitCPP.cpp
  In file included from */P1/Android//jni/CompilationUnitCPP.cpp:9:0:
  */P1/Android//jni/../../../Engine/Audio/AudioSystemAndroid.cpp:15:27: fatal error: SLES/OpenSLES.h: No such file or directory
  compilation terminated.
  </code></pre>
  
  <p>This happens to be the first foreign include I make. If I remove this include I get the same problem with stblib.h (!)</p>
  
  <p>I do not have this problem using identical project data under MacOS X</p>
  
  <p>I am especially perplexed how the tools can find the x86 headers and not the arm ones. I have seen this kind of configuration work fine several androids ago... I wonder if there has been some breaking change and there is now some Windows specific configuration that needs to be made.</p>
  
  <p>I've seen a few questions that look like my problem, but on close inspection are totally unrelated. This seems like such an obvious problem that I would not be surprised if there is a question and answer buried under all of the distractions...</p>