Hello.

I have external.so library. I can link and use it in my ndk library trough LOCAL_LDLIBS.
But it isnt static library so it should be copied to .apk for working together with my library.

I using android.mk and ndk-build build system so what i should write in android.mk for notice ndk-build i want this external.so be in apk ?

Hi, you can specify to ndk-build to add shared library with the line LOCAL_SHARED_LIBRARIES := external.
But you should rename your lib to libexternal.so because jni always look for a library like libNAME.so. And after you add your library to <project>/bin/ndl/YourPackage/. and in the libs/armeabi of your eclipse project.

I hope it answers to your problem.

+++

Thanx, but it doesnt work. LOCAL_SHARED_LIBRARIES should be used only for already defined libraries in same android.mk

No you can use it without creating the library in the Android.mk, here is an old file I wrote :

Code: Select all

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

LOCAL_MODULE := testso
LOCAL_SRC_FILES := testSO.c \

LOCAL_SHARED_LIBRARIES := meltingpot \
                    sgdlux

LOCAL_LDLIBS += -L$(SYSROOT)/usr/lib -ldl

include $(BUILD_SHARED_LIBRA

my libs meltingpot,sgdlux, are in the <project>/jni path, with the name : libmeltingpot.so and libsgdlux.so and my lisgdlux.so was not create by the ndk-build at all. And it works.

by

Interesting info about placing library, but at least for me
any LOCAL_SHARED_LIBRARIES generate make[1]: *** No rule to make target
(cygwin) and seems its very common problem for everyone

No rule to make target often means that ndk-build has not found the file, check your lib path to be sure they are stored in the good repository.

Interesting info about placing library, but at least for me
any LOCAL_SHARED_LIBRARIES generate make[1]: *** No rule to make target
(cygwin) and seems its very common problem for everyone

Indeed it is, but you guys gave handy enough argument that anyone can sort it out.