On Wed, Jun 9, 2010 at 11:55 AM, Ajith Kamath <sjce.aj...@gmail.com> wrote: > Ya I know all makefiles from External are called but I need to trace the > calls of make files from build script. > Atleast that of Bluez makefile. >
Yes this is sort of an eternal question ... we have the whole of build/core directory to understand !!! But then again ... not too many people in this list would prefer you using anything else apart from blueZ stack for Bluetooth ... - including me :) > Also BOARD_HAVE_BLUETOOH param is in Boardconfig.mk file right? yes.. typically somewhere in your vendor/ ... /BoardConfig.mk .. > Regards > Ajith > On Wed, Jun 9, 2010 at 11:40 AM, Pavan Savoy <pavan.sa...@gmail.com> wrote: >> >> i guess all android makefiles under external/<...>/ directory are called >> ... >> the only way you could prevent bluez from building is making >> BOARD_HAVE_BLUETOOH false ? (or atleast that's what i think ..) >> >> >> On Wed, Jun 9, 2010 at 9:22 AM, Ajith <sjce.aj...@gmail.com> wrote: >> > Hi all, >> > >> > Our current solution does not use Bluez stack in Android , but source >> > of Bluez is included in the Project Source code >> > >> > What I need to know is from where is the Make files of Bluez called >> > Android Eclair code. >> > ie, Android.mk file exists in \externals\bluetooth\bluez , and I need >> > to know where is this getting called from. >> > >> > If you can give me flow from mail build file itself, it would be >> > great. >> > >> > Regards, >> > Ajith >> > >> > -- >> > unsubscribe: android-porting+unsubscr...@googlegroups.com >> > website: http://groups.google.com/group/android-porting >> > >> >> >> >> -- >> --Pavan Savoy > > -- --Pavan Savoy -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
