Hi rktb
I follow your method and encounter the following error
Can you help me?

LOCAL_BUILT_MODULE and LOCAL_INSTALLED_MODULE must not be defined by
component makefiles.  Stop.

My 3'rd party's libraries are *.a.

On Feb 9, 12:07 pm, rktb <yend...@pv.com> wrote:
> Here you go...I verified that this works.
>
> ******************************************
> LOCAL_PATH := $(call my-dir)
> MY_LOCAL_PATH := $(LOCAL_PATH)
> include $(CLEAR_VARS)
>
> LOCAL_PREBUILT_LIBS := libabc.so
>
> include $(BUILD_MULTI_PREBUILT)
>
> LOCAL_PATH := $(MY_LOCAL_PATH)
> include $(CLEAR_VARS)
>
> LOCAL_SRC_FILES := main.cpp
> LOCAL_MODULE := mytest
> LOCAL_SHARED_LIBRARIES := libabc
>
> include $(BUILD_EXECUTABLE)
> ******************************************
>
> -Ravi
>
> On Feb 8, 9:39 pm, Girish <htgir...@gmail.com> wrote:
>
>
>
> > Hi all,
>
> > Replaced the same with LOCAL_PATH := $(call my-dir)
>
> > find: `build/core/clear_vars.mk,build/core': No such file or directory
> > make: execvp: /bin/bash: Argument list too long
> > target Strip: libdl (out/target/product/obj/lib/libdl.so)
> > Install: out/host/linux-x86/bin/vm-tests
> > make: *** No rule to make target `build/core/clear_vars.mk,build/
> > core', needed by `out/target/product/obj/EXECUTABLE
>
> > Anything to do with .so files ? main.c calls test.c and test.c calls
> > apis deineds libs 3 libs which try to link with my executable.. main.c
> > contains the entry point (int main ())
>
> > The libs are generated using arm-linux-eabi and with glibc2.2.
>
> > Wht may be the issue ?
>
> > Regards- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"android-framework" group.
To post to this group, send email to android-framework@googlegroups.com
To unsubscribe from this group, send email to 
android-framework+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to