blocks|key|3144712|text|据我所知，使用NDK的唯一原因是为了从您的应用程序中挤出额外的性能，并更接近裸机。如果你不需要做这两件事中的任何一件，你可能应该远离NDK。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3144713|还要注意的是，Dalvik+VM已经有了一些相当出色的性能，而且相对简单。|3144714|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The only reasons to use the NDK as far as I know is to squeeze extra performance out of your application and get closer to the bare metal. If you don't need to do either of these things, you should probably stay away from the NDK.

Also note that the Dalvik VM already has some pretty awesome performance and comparatively simpler.

blocks|key|250211|text|除非你有充分的理由使用NDK，否则你真的应该使用SDK。好的理由可能会有所不同，但例如，您可以使用NDK：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|250212|250213|如果你想使用OpenGL+ES+2.0+Android2.1+(Eclair)，它只能通过NDK获得。OpenGL+ES+2.0的开发工具包支持始于Froyo版本。|unordered-list-item|250214|如果你想使用|250215|，你有很大一部分应用程序的逻辑是用C/C%2B%2B|250216|编写的|250217|250218|entityMap^0|0|0|1|1|1|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|S|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

You really should use SDK, unless you have a good reason to use NDK. Good reasons may vary, but for example, you could use NDK:

<ul>
<li>If you want to use OpenGL ES 2.0 for Android 2.1 (Eclair), it is only avaiable through NDK. The SDK support for OpenGL ES 2.0 began with the Froyo version.</li>
<li>If you want to use Renderscript</li>
<li>If you have a great portion of your app's logic written in C/C++</li>
</ul>

blocks|key|250202|text|NDK在功能方面有更多的限制。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|250203|您可以从NDK中获得用C%2B%2B编写应用程序并将其编译为原生ARM代码的能力。如果您喜欢C%2B%2B胜过Java，如果您有一个想要移植到安卓的现有C%2B%2B应用程序，或者如果您只是需要只有本机代码才能提供的额外性能，那么无论如何都应该使用NDK。|250204|我自己没有这样做，但另一种选择是编写混合应用程序，其中应用程序主要是用Java语言编写的，其中选定的函数是用C%2B%2B编写的，这些函数是从Java语言代码中调用的。|250205|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The NDK is much more limited in terms of functionality.

What you do get from the NDK is the ability to write your app in C++ and compile it to native ARM code. If you like C++ better than Java, if you have an existing C++ app that you want to port to Android, or if you just need the extra performance that only native code can offer, then by all means you should use the NDK.

I haven't done this myself, but another alternative is to write hybrid app, where the app is written mostly in Java, with selected functions written in C++ that are called from the Java code.

blocks|key|2930148|text|对我来说，我认为了解NDK很重要，它是移动应用程序开发中的一个强大工具。尤其是如果你想开发一个多平台的应用程序，NDK在这个领域是无与伦比的。因为用C%2B%2B编写的代码可以很容易地移植到iOS、Windows或任何其他平台上运行，而不需要更改原始代码。这实际上在为在多个平台上运行而开发的应用程序的开发中节省了大量时间；例如游戏和其他经典应用程序。使用SDK不能做的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2930149|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me, I think it’s important to know the NDK which is a powerful tool in the development of mobile applications. Especially if you want to develop a multiplatform application, the NDK is unbeatable in this domain. Since the same code written in C + + for Android can be easily ported and run the same way on the iOS, Windows or any other platform without changing the original code. Which actually save a lot of time in the development of applications which are developed for being run on multiple platforms; as games and other classic applications. Thing you cannot do with the SDK.

blocks|key|250263|text|本机方法是特定于平台的代码。它们通常是用C或C%2B%2B等语言编写的，并包含在库(Dll)中。可以创建从这些库中受益的混合Java应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|250264|使用本机方法的原因|offset|length|style|BOLD|250265|250266|获得设备或/或安卓操作系统的特殊功能|ordered-list-item|250267|获得额外的速度|250268|获得对大量现有旧代码的访问权限|250269|250270|通常，NDK的良好用例是CPU密集型应用程序，如游戏引擎、信号处理和物理模拟|250271|原生方法的主要缺点是没有跨平台能力。|250272|现在，如果您不知道本机代码是什么，那么您可能不需要使用本机代码。Android+NDK文档很好地解释了这一点：|250273|NDK+...，你应该明白|250274|不会让大多数应用程序受益。作为一名开发人员，您需要权衡它的优点和缺点。值得注意的是，在Android上使用原生代码通常不会带来显著的性能改进，但它总是会增加应用程序的复杂性。一般来说，您应该只使用NDK，如果它对您的应用程序是必要的-永远不要，因为您只是更喜欢用C/C%2B%2B编程。在检查您是否应该使用本机代码进行开发时，请考虑您的需求，并查看Android框架API是否提供了您需要的功能。|blockquote|250275|250276|entityMap^0|0|7|2|0|0|0|I|0|0|7|0|0|F|0|0|0|12|0|0|I|0|0|1J|0|0|D|0|0|5E|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|L|3|M|5|K|7|1C|8|@$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|N|3|O|5|K|7|1F|8|@$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1J|8|@$D|1K|E|1L|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1M|8|@$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1P|8|@$D|1Q|E|1R|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1S|8|@$D|1T|E|1U|F|G]]|9|@]|A|$]]|$1|Y|3|Z|5|10|7|1V|8|@$D|1W|E|1X|F|G]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]]|13|$]]

Native methods are platform-specific code. They are usually written in languages such as C or C++ and contained in libraries(dll's). It is possible to create a hybrid Java application that benefits from such libraries.

Reasons for Using Native Methods

<ol>
<li>Gaining access to special capabilities of your device or or Android
OS </li>
<li>Gaining extra speed </li>
<li>Gaining access to a large body of existing legacy code</li>
</ol>

Typically, good use cases for the NDK are CPU-intensive applications such as game engines, signal processing, and physics simulation

The major disadvantage of native methods is that you won't have cross-platform capability.

Now if you don't know what native code is, then probably you don't need to use native code. Android NDK documentation explains this well:

<blockquote>
 ..., you should understand that the NDK will not benefit most apps. As
 a developer, you need to balance its benefits against its drawbacks.
 Notably, using native code on Android generally does not result in a
 noticable performance improvement, 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++. 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.
</blockquote>

I am about to start android application development.
From <a href="http://developer.android.com/sdk/ndk/overview.html" rel="nofollow noreferrer">What is NDK?</a> documentation I was not able to extract the following information:
Does using NDK actually introduce new features comparing to SDK?
I am interested in this because using NDK greatly increases application complexity, so if I am not interested in performance increase, are there other reasons to go for NDK?
What I mean is for example:
-restart phone
<ul>
<li>(I know neither SDK nor NDK allows this, I just use it as an example of what I mean) let's say java SDK does not allow this, but some native libraries do - then the answer to my question would be yes, NDK does add some functionality</li>
</ul>
Thanks in advance for any helpful answers.

What is the difference between Android SDK and NDK?

移动应用程序开发

游戏引擎

Android

Windows

Java

我即将开始android应用程序的开发。从文档中，我无法提取以下信息：与SDK相比，使用NDK真的引入了新功能吗？我对此很感兴趣，因为使用NDK会极大地增加应用程序的复杂性，所以如果我对提高性能不感兴趣，还有其他理由去使用NDK吗？我的意思是举个例子：-restart电话(我知道SDK和NDK都不允许这样做，我只是用它作为我的意思的一个例子)假设java SDK不允许这样做，但一些本地库允许-那么

问Android SDK和NDK有什么区别？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android SDK和NDK有什么区别？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android SDK和NDK有什么区别？
EN