Lines Matching full:code
73 <li>Provides a simplified build system through the new <code>ndk-build</code> build
75 <li>Adds support for easy native debugging of generated machine code on production
76 devices through the new <code>ndk-gdb</code> command.</li>
78 <code>armeabi-v7a</code>. The new ABI extends the existing <code>armeabi</code>
87 <li>Adds a new <code>cpufeatures</code> static library (with sources) that lets
90 support, then provide separate code paths as needed.</li>
91 <li>Adds a sample application, <code>hello-neon</code>, that illustrates how to
92 use the <code>cpufeatures</code> library to check CPU features and then provide
93 an optimized code path using NEON instrinsics, if
95 <li>Lets you generate machine code for either or both of the instruction sets
98 final <code>.apk</code>.</li>
108 code.</li>
127 <li>Adds a sample application,<code>hello-gl2</code>, that illustrates the use of
129 <li>The toolchain binaries have been refreshed for this release with GCC 4.4.0, which should generate slightly more compact and efficient machine code than the previous one (4.2.1). The NDK also still provides the 4.2.1 binaries, which you can optionally use to build your machine code.</li>
148 <li>Adds a sample application, <code>san-angeles</code>, that renders 3D
184 of native code in your Android applications.
188 you to implement parts of your applications using native-code languages
190 in the form of reuse of existing code and in some cases increased speed.</p>
195 <li>A set of tools and build files used to generate native code libraries from C
198 file (<code>.apk</code>) that can be deployed on Android devices</li>
217 <p>ARMv5TE machine code will run on all ARM-based Android devices. ARMv7-A will
225 stored in the final <code>.apk</code>. For complete information is provided in the
233 to balance its benefits against its drawbacks; notably, using native code does
239 an effective way to reuse a large corpus of existing C/C++ code.</p>
284 <code><ndk>/docs/</code> directory. Included are these files:</p>
303 <li>CPU-FEATURES.TXT — a description of the <code>cpufeatures</code>
304 static library that lets your application code detect the target device's
315 <code><ndk>/docs/system/libc/</code> directory:</p>
325 native code in your Android applications. For more information, see
369 href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"><code><uses-sdk></code></a>
370 element in its manifest file, with an <code>android:minSdkVersion</code> attribute
384 <code>android:minSdkVersion</code></a> attribute value, as given in the table.</p>
392 <tr><td>OpenGL ES 1.1</td><td>Android 1.6 and higher</td><td><code>android:minSdkVersion="4"</code></td></tr>
393 <tr><td>OpenGL ES 2.0</td><td>Android 2.0 and higher</td><td><code>android:minSdkVersion="5"</code></td></tr>
401 <code><uses-feature></code> element in its manifest, with an
402 <code>android:glEsVersion</code> attribute that specifies the minimum OpenGl ES
416 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code></a>
423 declares <code><uses-sdk android:minSdkVersion="8" /></code>attribute
446 <code>android-ndk-<version></code>. You can rename the NDK directory if
448 documentation refers to the NDK directory as <code><ndk></code>. </li>
457 <code><ndk>/docs/</code> directory. In particular, please read the
468 <code><project>/jni/...</code></li>
469 <li>Create <code><project>/jni/Android.mk</code> to
471 <li>Optional: Create <code><project>/jni/Application.mk</code>.</li>
472 <li>Build your native code by running the 'ndk-build' script from your projet's directory.
486 deployable <code>.apk</code> file. </p></li>
497 code in your Android applications:</p>
500 <li><code>hello-jni</code> — a simple application that loads a string from
503 <li><code>two-libs</code> — a simple application that loads a shared
507 <li><code>san-angeles</code> — a simple application that renders 3D
510 <li><code>hello-gl2</code> — a simple application that renders a triangle
512 <li><code>hello-neon</code> — a simple application that shows how to use
513 the <code>cpufeatures</code> library to check CPU capabilities at runtime,
517 <li><code>bitmap-plasma</code> — a simple application that demonstrates
519 objects from native code, and uses this to generate an old-school "plasma"
523 <p>For each sample, the NDK includes the corresponding C source code and the
525 <code><ndk>/samples/<name>/</code> and their source code can be found under
526 <code><ndk>/samples/<name>/jni/</code>. </p>
528 <p>You can build the shared libraries for the sample apps by going into <code><ndk>/samples/<name>/</code>
529 then calling the <code>ndk-build</code> command. The generated shared libraries will be located under
530 <code><ndk>/samples/<name>/libs/armeabi/</code> for (ARMv5TE machine code) and/or
531 <code><ndk>/samples/<name>/libs/armeabi-v7a/</code> for (ARMv7 machine code).
541 <code><ndk>/apps/<app_name>/project/</code>. Then, set up an AVD, if
546 <li>If you are developing with Ant, use the <code>android</code> tool to create
548 <code><ndk>/apps/<app_name>/project/</code>. Then set up an AVD, if
