diff options
| author | Vince Harron <vharron@google.com> | 2014-04-25 23:22:07 +0000 |
|---|---|---|
| committer | Android Git Automerger <android-git-automerger@android.com> | 2014-04-25 23:22:07 +0000 |
| commit | 4f50911aa18f9d4650c6721456dd05ac499fcefd (patch) | |
| tree | 2d708bdcb4fd20b46a406d32b7bf2a0d446f7094 /docs | |
| parent | 6fe328c62abd3b98aceeeb99aaf5d824bd42adc6 (diff) | |
| parent | e9a4e9deaad6a3185269bf5696c2a2946962fbd2 (diff) | |
| download | frameworks_base-4f50911aa18f9d4650c6721456dd05ac499fcefd.zip frameworks_base-4f50911aa18f9d4650c6721456dd05ac499fcefd.tar.gz frameworks_base-4f50911aa18f9d4650c6721456dd05ac499fcefd.tar.bz2 | |
am e9a4e9de: Merge "Clarified recommended use cases for NDK. Added - "game engines" officially supported use case for NDK Removed - "self-contained" ambiguous in general and confusing to someone who is trying to do game development in C++ Removed - "that don\'t allocat
* commit 'e9a4e9deaad6a3185269bf5696c2a2946962fbd2':
Clarified recommended use cases for NDK. Added - "game engines" officially supported use case for NDK Removed - "self-contained" ambiguous in general and confusing to someone who is trying to do game development in C++ Removed - "that don't allocate a lot of memory" game engines do allocate a lot of memory.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/html/tools/sdk/ndk/index.jd | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/html/tools/sdk/ndk/index.jd b/docs/html/tools/sdk/ndk/index.jd index a22dc90..0ac1881 100644 --- a/docs/html/tools/sdk/ndk/index.jd +++ b/docs/html/tools/sdk/ndk/index.jd @@ -245,8 +245,8 @@ This is the Android Software Development Kit License Agreement but it always increases your app complexity. In general, you should only use the NDK if it is essential to your app—never because you simply prefer to program in C/C++.</p> - <p>Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't - allocate much memory, such as signal processing, physics simulation, and so on. When examining + <p>Typical good candidates for the NDK are CPU-intensive workloads such as game engines, + signal processing, physics simulation, and so on. When examining whether or not you should develop in native code, think about your requirements and see if the Android framework APIs provide the functionality that you need.</p> |