The NDK sample project two-libs shows how to do this:
LOCAL_PATH:= $(call my-dir)
# first lib, which will be built statically
LOCAL_MODULE := libtwolib-first
LOCAL_SRC_FILES := first.c
# second lib, which will depend on and include the first one
LOCAL_MODULE := libtwolib-second
LOCAL_SRC_FILES := second.c
LOCAL_STATIC_LIBRARIES := libtwolib-first
On Monday, September 17, 2012 4:46:44 AM UTC-4, Vijay Bhaskar wrote:
your idea, looks good. keeping one shared library and others as static .
can you please give example interms Android.mk file.
On Thursday, September 30, 2010 11:00:23 PM UTC+5:30, Kelly wrote:
If you have a BUILD_SHARED_LIBRARY in your top level with
LOCAL_STATIC_LIBRARIES := (Other libs) and all the other libraries are
BUILD_STATIC_LIBRARY, you will only generate one shared library and
only have to load that.
> In my case, i have to load both of them using system.loadlibrary, and
> remember to load B first, then A
> On Sep 30, 2010 6:00 PM, "Jerry Yin" <[hidden email]> wrote:
> In this case, is that the libB need to be build as static library? If not,
> is it necessary to load both libA and libB using System.loadLibrary()? Or
> the libB will be automatically loaded?
> On Thu, Sep 30, 2010 at 6:04 AM, David Turner <[hidden email]> wrote:
> > You can have as many An...
> You received this message because you are subscribed to the Google Groups
> "android-ndk" group.
> To po...