title: Android build system, NEON and non-NEON builds
body: <p>I want to build my library for armv6, and there is some neon code that I enable at runtime if the device supports it. The neon code uses neon intrinsics, and to be able to compile it, I must enable armeabi-v7a, but that affects regular c-code (it becomes broken on some low-end devices).</p>
  
  <p>So, if the android build system wasn't excessively intrusive, I wouldn't have to ask questions, but it seems that there is no way for me to compile one file for armv6 and the other file for arm7-neon.</p>
  
  <p>Can anybody give any clues if that's doable?</p>
  
  <p><strong>Edit</strong><br/>
  Before trying to reply and wasting internet-ink, it should be clear that these are the main points: <br/>
   <strong>1)</strong> make only ONE lib.<br/>
   <strong>2)</strong> make build that runs on armv6 (pre neon devices, e.g. armeabi).<br/>
   <strong>3)</strong> allow this build to also contain NEON code (which could be executed based on run-time cpu detection; cpu detection is outside the scope of the question).<br/>
   <strong>4)</strong> NEON code comes from a c/cpp file and is written using neon intrinsics.<br/></p>
  
  <p><strong>Omitting any part of these requirements totally loses the point of the question</strong></p>