Question: How to static link boost to an app ?

[moritz-wundke]

Question: How to static link boost to an app ?

[bk138]

Right, I think LDLIBS is for shared libraries only. In my case, the build script just built .a static libs.

You'll have to define a module for the static library and use this for linking

#
#
TOP_LOCAL_PATH := $(call my-dir)
include $(call all-subdir-makefiles)

LOCAL_PATH := $(TOP_LOCAL_PATH)


# define static boost threads lib
include $(CLEAR_VARS)
LOCAL_MODULE    := libboost_thread.
LOCAL_SRC_FILES := boost-for-android/lib/libboost_thread-gcc-mt-1_49.a
include $(PREBUILT_STATIC_LIBRARY)


# now libaweseome shared lib
include $(CLEAR_VARS)
LOCAL_CPPFLAGS += -I$(LOCAL_PATH)/boost-for-android/include/boost-1_49
#LOCAL_LDLIBS += -L$(SYSROOT)/usr/lib -llog.

LOCAL_MODULE    := awesome
LOCAL_SRC_FILES := Source.cpp Source2.cpp
LOCAL_STATIC_LIBRARIES := libboost_thread


include $(BUILD_SHARED_LIBRARY)

Ok thanks for the little sample :)

I think the result is concretely the same whether you use LDLIBS or LOCAL_STATIC_LIBRARIES. I assume they just piggyback on LDLIBS to add the "-lblablabla" parameter to the command line.

I thought (and I was wrong) it was somehow enforced somewhere, but it's not.

I think using LOCAL_STATIC_LIBRARIES and defining a module is more academic however :) (that's what I did)