android is a monolithic build system and nested around whole directory structure, making it tough to track manually.
it all starts from <mydroid>/build/main.mk, build walks through complete directory structure, calculate dependencies, and starts building.. anyways, you can get description and usage of Android.mk files in android site. i did this when i was adding a new shared library: - Make sure your Android.mk is included during build process (done by adding to upper directories Android.mk or parent directory should have add-all-sub-folder script) - wait for build to break or in a perfectly working build, introduce garbled character in my moudles Android.mk, make it to fail, then track back from log.. Havent dugg much, once i got stuff working (so simple to introduce new module though :> ) On Fri, Mar 26, 2010 at 10:01 AM, Neo <zingafri...@yahoo.com> wrote: > > > On Mar 19, 9:21 am, chungae9ri <chungae...@gmail.com> wrote: >> Hi, I am analyzing the build flow of android. >> I inserted the messages like print log and I lost after the build/core/ >> main.mk. >> what is the next step or makefile that is executed after main.mk? > > The build is a huge set of nested makefiles. Your prints can get lost > in the environment which gets called in different stages. > Better option would be analyse the make dependencies and make a tree. > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > > To unsubscribe from this group, send email to > android-porting+unsubscribegooglegroups.com or reply to this email with the > words "REMOVE ME" as the subject. > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting To unsubscribe from this group, send email to android-porting+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
