The Android NDK guide explains the two variables in the Adnroid.mk
as follows:
LOCAL_LDLIBS - The list of additional linker flags to be used when building your shared library or executable.
...
LOCAL_LDFLAGS - The list of other linker flags to be used when building your shared library or executable.
...
So what is the difference between these two?
LOCAL_LDFLAGS - The list of other linker flags to be used when building your shared library or executable.
Overview. The Android.mk file resides in a subdirectory of your project's jni/ directory, and describes your sources and shared libraries to the build system. It is really a tiny GNU makefile fragment that the build system parses once or more.
The main differences are the following:
LOCAL_LDFLAGS appear before the list of object files and libraries on the final linker command-line, this is where you want to put actual "flags" that affect linker behaviour.
LOCAL_LDLIBS appear after the list of object files and libraries on the final linked command-line, this is where you want to put actual system library dependencies.
The distinction exists because of the way static linking works on Unix, i.e. the order of object files, static libraries and shared libraries is very important to determine the final result, and sometimes you really to ensure that something appears before / after the other.
In the end, I recommend following the documentation, i.e.:
Put real linker flags into LOCAL_LDFLAGS
Put system library dependencies into LOCAL_LDLIBS
Only use LOCAL_LDLIBS for system library dependencies. If you want to point to another library, it's much better to list them in either LOCAL_STATIC_LIBRARIES and LOCAL_SHARED_LIBRARIES (even if this means defining a PREBUILT_XXX module for them), because this lets the build system work out dependencies and ordering automatically for you.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With