LineageOS/android_development
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

am 3d25a3b: More Clean up in the NDK Overview doc

Browse Source 
Merge commit '3d25a3b264fdf7422fe840a03e88944423edacc5'

* commit '3d25a3b264fdf7422fe840a03e88944423edacc5':
  More Clean up in the NDK Overview doc
This commit is contained in:
Xavier Ducrohet
2009-05-08 22:49:31 -07:00
committed by The Android Open Source Project
parent ed3d5cb836 3d25a3b264
commit 80f95f21a7
1 changed files with 8 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
ndk/docs/OVERVIEW.TXT
View File

@@ -17,11 +17,10 @@ IMPORTANT:
I. Android NDK Goals: I. Android NDK Goals:
--------------------- ---------------------
The Android VM allows your application's Java source code to call methods The Android VM allows your application's source code to call methods
implemented in native code through the Java Native Interface (JNI). In a implemented in native code through the JNI. In a nutshell, this means that:
nutshell, this means that:
- Your application's Java source code will declare one or more methods - Your application's source code will declare one or more methods
with the 'native' keyword to indicate that they are implemented through with the 'native' keyword to indicate that they are implemented through
native code. E.g.: native code. E.g.:
@@ -36,7 +35,7 @@ nutshell, this means that:
libFileLoader.so libFileLoader.so
- Your application must explicitely load the library. For example, to load - Your application must explicitely load the library. For example, to load
it at application startup, simply add the following to its Java source code: it at application startup, simply add the following to its source code:
static { static {
System.loadLibrary("FileLoader"); System.loadLibrary("FileLoader");
@@ -85,12 +84,12 @@ II. Android NDK Non-Goals:
The NDK is *not* a good way to write generic native code that runs on Android The NDK is *not* a good way to write generic native code that runs on Android
devices. In particular, your applications should still be written in the Java devices. In particular, your applications should still be written in the Java
language, handle Android system events appropriately to avoid the programming language, handle Android system events appropriately to avoid the
"Application Not Responding" dialog or deal with the Android application "Application Not Responding" dialog or deal with the Android application
life-cycle. life-cycle.
Note however that is is possible to write a sophisticated application in Note however that is is possible to write a sophisticated application in
native code with a small "Java application wrapper" used to start/stop it native code with a small "application wrapper" used to start/stop it
appropriately. appropriately.
A good understanding of JNI is highly recommended, since many operations A good understanding of JNI is highly recommended, since many operations
@@ -176,7 +175,7 @@ The NDK build system expects your sources to be visible under the top-level
You are pretty free to organize the content of 'sources' as you want, You are pretty free to organize the content of 'sources' as you want,
the directory names and structure here will not influence the final the directory names and structure here will not influence the final
generated application packages, so you don't have to use pseudo-unique generated application packages, so you don't have to use pseudo-unique
names like com.<mycompany>.<myproject> as is the case for Java application names like com.<mycompany>.<myproject> as is the case for application
package names. package names.
For the record, the NDK comes with a 'sources/samples' directory which For the record, the NDK comes with a 'sources/samples' directory which
@@ -239,7 +238,7 @@ Where <myapp> is a short descriptive name for your application that will
be used to invoke the NDK build (and not go into final APKs). The file is be used to invoke the NDK build (and not go into final APKs). The file is
used to provide the following to the NDK build: used to provide the following to the NDK build:
- The location of your Java application's project path - The location of your Android application's project path
- The list of NDK modules that is required by your application. - The list of NDK modules that is required by your application.
This should really be a list of 'shared library' modules. This should really be a list of 'shared library' modules.