title: Android ndk-build not generating gdb.setup file
body: <p>I am currently trying to debug native code in Android via ndk-gdb but I am having some troubles. 
  Even if I start a very simple project (let's say for example a default cocos2d-x v3 project) and run </p>
  
  <pre><code>ndk-build NDK_DEBUG=1
  </code></pre>
  
  <p>I end up with the following folder structure inside my android project</p>
  
  <pre><code>...
  libs/
      armeabi/
          libcocos2dcpp.so
  ...
  </code></pre>
  
  <p>instead of the expected:</p>
  
  <pre><code>...
  libs/
      armeabi/
          gdb.setup
          gdbserver
          libcocos2dcpp.so
  ...
  </code></pre>
  
  <p>In order to use ndk-gdb I need those two gdb files.</p>
  
  <p>I am using cocos version 3.2 and Android NDK version r9d.</p>
  
  <p>Isn't <code>NDK_DEBUG=1</code>enough for the gdb files to be generated? I have also tried with<code>android:debuggable="true"</code> inside my manifest file but it didn't work.</p>
  
  <p><strong>Edit</strong></p>
  
  <p>After running the command suggested by Digit I found a very suspicious line</p>
  
  <pre><code>Android NDK: Application 'local' forced *not* debuggable through NDK_DEBUG
  </code></pre>
  
  <p>when running the command <code>ndk-build NDK_LOG=1 NDK_DEBUG=1</code></p>
  
  <p>BUT</p>
  
  <p>if I change to <code>ndk-build NDK_LOG=1 NDK_DEBUG=true</code> I get</p>
  
  <pre><code>Android NDK: Application 'local' forced debuggable through NDK_DEBUG
  </code></pre>
  
  <p>So it is ok now, really weird though how <code>=1</code> is not considered true.</p>