Applied in changeset commit:71a2cb729264a7a90b74517be2a2745a50a5a977.

@Surith said
>> Using shell commands in a makefile is fine if we are building on a known system. However Cocos is built on multiple platforms (Linux, OSX, Windows) each of which could have different shells (bash, Cygwin bash) and with different versions of find, with different line endings (windows vs. unix line endings), etc. The situation is further complicated by user customizations. For example, some users will change the default shell to ‘C’ shell which will affect the shell command in GNU Make.

>> Is it necessary to auto generate file dependencies? Yes it is tedious to maintain lists of source files in Android.mk but it is also simple.It is better than having to debug problems in makefiles caused by unknown platforms.

>> So, I would recommend keeping makefiles as dumb lists.

>> If we do need to auto-generate makefiles we should use a platform that is designed to work the same across different environments - such as Python + GyP.

And i think it is right. We should use less platform-dependent codes. So i will change the title and create tools to auto-generate Android.mk.

Applied in changeset commit:16c246cab040248fefbb0e7682b67480c97b2e41.