Android.mk vs Application.mk

Question

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

I\'ve tried reading APPLICATION-MK.HTML & ANDROID-MK.HTML in the documentation that comes with N

Answer 1

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.