drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am 4f50911a: 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

Browse Source 
* commit '4f50911aa18f9d4650c6721456dd05ac499fcefd':
  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.
This commit is contained in:
Vince Harron
2014-04-25 23:25:11 +00:00
committed by Android Git Automerger
parent 9d7c58cf8b 4f50911aa1
commit 165b965edb
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/html/tools/sdk/ndk/index.jd
View File

@ -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&mdash;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>