Android NDK中dlopen()路径问题求助：用完整路径还是应用内库名？

Great question! Let me break down how dlopen() works with paths on Android NDK, since it’s a common point of confusion depending on where your library is stored.

Scenario 1: Using just the library name (no path) #

This works only for libraries packaged with your app (the ones you place in jniLibs/[ABI]/ or libs/[ABI]/ during development). When you build and install your app, these libraries are copied to your app’s private native library directory (usually /data/app/[your-package-name]/lib/[ABI]/), which is automatically included in the dynamic linker’s search path for your app’s process.

You can use either:

• The full library filename (e.g., "libmylib.so")
• The short name (without lib prefix or .so suffix, e.g., "mylib" — the linker will automatically add the prefix/suffix for you)

Example code snippet:

#include <dlfcn.h>
#include <android/log.h>

void loadAppLibrary() {
    // Load using full filename
    void* handle = dlopen("libmylib.so", RTLD_NOW);
    if (!handle) {
        __android_log_print(ANDROID_LOG_ERROR, "DL_DEBUG", "Failed to load libmylib.so: %s", dlerror());
        return;
    }

    // Do something with the library...
    dlclose(handle);
}

Scenario 2: Using a full absolute path #

You must use a full absolute path if your library is stored outside the app’s default native library directory. Common examples include:

• Libraries saved to your app’s private files/ directory
• Libraries loaded from external storage (with proper permissions)
• Custom library locations you’ve created

Important notes here:

• Always use Android’s API to get valid paths (never hardcode paths like /data/data/your.package/ — these can change between Android versions or device configurations).
• Ensure your app has read permissions for the target directory (e.g., READ_EXTERNAL_STORAGE for external storage, though private app directories don’t require extra permissions).

Example code snippet (loading from app’s files directory):

#include <dlfcn.h>
#include <android/log.h>
#include <jni.h>
#include <string.h>

JNIEXPORT void JNICALL
Java_com_yourpackage_MainActivity_loadCustomLibrary(JNIEnv* env, jobject thiz) {
    // Get app's files directory path from Java
    jclass activity_cls = env->GetObjectClass(thiz);
    jmethodID get_files_dir = env->GetMethodID(activity_cls, "getFilesDir", "()Ljava/io/File;");
    jobject file_obj = env->CallObjectMethod(thiz, get_files_dir);
    jclass file_cls = env->FindClass("java/io/File");
    jmethodID get_abs_path = env->GetMethodID(file_cls, "getAbsolutePath", "()Ljava/lang/String;");
    jstring path_str = (jstring)env->CallObjectMethod(file_obj, get_abs_path);
    const char* files_path = env->GetStringUTFChars(path_str, NULL);

    // Build full path to the custom library
    char full_path[256];
    snprintf(full_path, sizeof(full_path), "%s/libcustom.so", files_path);

    // Load the library
    void* handle = dlopen(full_path, RTLD_NOW);
    if (!handle) {
        __android_log_print(ANDROID_LOG_ERROR, "DL_DEBUG", "Failed to load %s: %s", full_path, dlerror());
    } else {
        __android_log_print(ANDROID_LOG_INFO, "DL_DEBUG", "Successfully loaded %s", full_path);
        dlclose(handle);
    }

    // Clean up JNI references
    env->ReleaseStringUTFChars(path_str, files_path);
    env->DeleteLocalRef(file_obj);
    env->DeleteLocalRef(file_cls);
    env->DeleteLocalRef(activity_cls);
}

Key Takeaways #

• App-packaged libraries: Use just the library name (either full filename or short name) — no path needed.
• Custom location libraries: Always use the full absolute path, retrieved via Android’s official APIs.
• Avoid hardcoding paths to ensure compatibility across Android versions and devices.

内容的提问来源于stack exchange，提问作者Ryan Ferreira