Android.mk VS Application.mk [英] Android.mk vs Application.mk

问题描述

我对使用Android.mk＆放的有点模糊; Application.mk

I'm a little fuzzy about the use of Android.mk & Application.mk

我试着阅读应用，MK.HTML和放大器; Android的MK.HTML附带NDK 的文档中，但仍然感到困惑的目的两个 makefile文件。

I've tried reading APPLICATION-MK.HTML & ANDROID-MK.HTML in the documentation that comes with NDK, but still confused about the purpose of two makefiles.

我会很感激的人谁可以帮助我理解这一点。

I'll be really grateful to anyone who could help me understand this.

推荐答案

每个模块都需要有且仅有一个Android.mk。如果你曾经有在你的本机应用程序一个模块中，Application.mk是多余的（但是也有由Application.mk如果从默认行为转向，只能控制一些事情）。但是，如果你有很多模块，ERGO许多Android.mk文件在您的项目，比Application.mk可提供适用于所有模块的应用程序范围的设置非常有用。

Each module requires one and only one Android.mk. If all you ever have is one module in your native application, the Application.mk is redundant (however there are a few things that can only be controlled by the Application.mk if you veer from default behavior). However, if you have many modules, ergo many Android.mk files in your project, than the Application.mk can be useful for providing application-wide settings that apply to ALL modules.

这篇关于Android.mk VS Application.mk的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！