Trimming content for brevity ... > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Mathieu Desnoyers ... > * Xing Fan ([email protected]) wrote: ... > > I still think there is something wrong in my Android.mk file. If we read > > Makefile.am, it indicates to build a shared library called libust based on > > libust-initializer (I have treated this in my Android.mk). However, it seems > > Makefile does more than this. it builds/uses libust-initializer.o, I do not > > know how to put this in Android.mk file. > > > > Anyone has any hint? > > Sorry, I'm not familiar with the Android build infrastructure. Maybe > Karim might have some info here ? (see problem description below)
I don't have enough information. Has libust been placed in aosp/external/. That's where it would usually go. Usually the best thing is to check how other packages in external/ are made to build part of the AOSP and do the same. As for the libust-initializer.c getting picked up, it looks like it's the EXTRA_DIST flag from Makefile.am creeping in. Again, I would need more info. -- Karim Yaghmour CEO - Opersys inc. / www.opersys.com http://twitter.com/karimyaghmour _______________________________________________ ltt-dev mailing list [email protected] http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
