* Xing Fan ([email protected]) wrote: > Here are more description of my setting. > 1. I placed the ust code in external/ folder. > 2. my Android.mk file in external/ust-0.6 looks like this: > =========================================================== > include $(call all-subdir-makefiles) > > LOCAL_PATH := $(call my-dir) > > include $(CLEAR_VARS) > LOCAL_MODULE := libust > LOCAL_SRC_FILES := libust-initializer.c > LOCAL_C_INCLUDES += \ > $(LOCAL_PATH) \ > $(LOCAL_PATH)/include \ > external/userspace-rcu-0.4.6 > include $(BUILD_SHARED_LIBRARY) > =============================================================== > > 3. However, I have problems to build libust.so. The error msg is: make: > *** No rule to make target `build/core/libust-initializer.c', needed by > `out/target/product/u8500/obj/SHARED_LIBRARIES/libust_intermediates/libust-initializer.o'. > Stop. > > It is very strange that the compiler tries to pick up > libust-initializer.c from build/core folder, even though I have specified > that the source file is in my LOCAL_PATH, which is external/ust-0.6;
Again, please retry with updated liburcu and UST, as ust 0.6 does not support ARM. We might be lucky and a fix might have crept in the tree since 0.6, so let's not spend time debugging old versions. Thanks, Mathieu > > /Stella > > On Wed, Apr 20, 2011 at 11:12 PM, Karim Yaghmour <[email protected] > > wrote: > > > 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 > > -- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com _______________________________________________ ltt-dev mailing list [email protected] http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
