Thanks David for your answer! Regards, Kishor
On Fri, Jan 9, 2009 at 5:51 PM, David Turner <[email protected]> wrote: > You don't need one Android.mk per sub-directory. It's perfectly possible to > use one top-level Android.mk > that references all sources required for your project. just refer to them > with their subpath, as in subdir/filename. > > and no, it's not possible to convert an arbitrary Makefile into an > Android.mk (especially the bizarre convolutions > used/generated with Automake). The good news is that writing an Android.mk > file is not very difficult as long as > you know which files you want to build. > > > On Fri, Jan 9, 2009 at 7:29 AM, krish24 <[email protected]> wrote: > >> >> Hi Everyone, >> >> I am trying to port a package (library) in android. There are many >> subfolder in my library folder and each subfolder contains a makefile. >> I know that we have to write Android.mk file for building the package. >> Do we need to write the Andriod.mk file for each subfolder present in >> my library. Is there any way to generate Android.mk file from standard >> makefile? >> >> Regards, >> Krish >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
