20

My app has the following structure

Android
|
|-> app
|    |
|    |-> build [1]
|    |-> src
|    |    |-> main
|    |    |     |-> assets
|    |    |     |-> java
|    |    |     |-> jni 
|    |    |     |     |-> Android.mk
|    |    |     |     |-> Application.mk
|    |    |     |
|    |    |     |-> jniLibs
|    |    |     |      |-> armeabi
|    |    |     |      |-> armeabi-v7a
|    |    |     |
|    |    |     |-> res
|    |    |     |-> AndroidManifest.xml
|
|-> build [2]

I am building my .so libraries with ndk-build command in a linux machine. I use it like:

<my_ndk_path>/ndk-build -C <my_project_path>/Android/app/src/main/

The build process works fine and output files are produced with no errors.

My problem is that the result files are not "directed to the proper position"

The libs generated at :

.app/src/main/libs/armeabi-v7a/libMyGeneratedLibrary.so
.app/src/main/libs/armeabi/libMyGeneratedLibrary.so

and the obj files at :

.app/src/main/obj/local/armeabi-v7a/libMyGeneratedLibrary.so
.app/src/main/obj/local/armeabi/libMyGeneratedLibrary.so

I would like the output to produced in different locations:

  1. The libs at jniLibs. ie. ./app/src/main/jniLibs/armeabi*
  2. The obj under one of the build folders. ie. build[1] or build[2].

Is there any possible way to achieve that by changing some parameter to the .mk files or to the build command?

Edit

TARGET_OUT does not seem to work in NDK r6b

Executing command ndk-build -C Android/app/src/main/ TARGET_OUT='Android/app/src/main/jniLibs/$(TARGET_ARCH_ABI)'

Warnings as the following appear for each generated file.

android-ndk-r6b/build/core/build-binary.mk:217: warning: overriding commands for target 'Android/app/src/main/jniLibs//objs/***/****.o'
android-ndk-r6b/build/core/build-binary.mk:217: warning: ignoring old commands for target 'Android/app/src/main/jniLibs//objs/***/****.o'
4

5 回答 5

35

You can use NDK_LIBS_OUT to change libs output and NDK_OUT to change obj output. Just like this : ndk-build NDK_LIBS_OUT=./jniLibs NDK_OUT=./obj

于 2015-07-07T09:57:19.380 回答
5

If you need to build for all available architectures, please use argument:

    TARGET_OUT='<your_build_dir>/$(TARGET_ARCH_ABI)'

If just one target architecture is enough, then use argument:

    TARGET_OUT=<your_build_dir>
于 2015-08-10T14:12:36.057 回答
2

The better and more simple way to specify out put locations is linking Gradle to your native library. After that, using buildStagingDirectory options in ndkBuild block to specify out put location:

android {
    externalNativeBuild {
        ndkBuild {
            // Tells Gradle to put outputs from external native
            // builds in the path specified below.
            buildStagingDirectory  "src/main/libs"
        }
    }
}

Then just Sync Gradle and build, done.

于 2020-03-02T15:57:08.777 回答
0

Edit (for anyone that step on this topic with newer NDK versions):

  • Use NDK_LIBS_OUT to change libs output (requires NDK r9 and above)
  • Use NDK_OUT to change obj output (requires NDK r7c and above)

Build command is is:

ndk-build NDK_LIBS_OUT=./jniLibs NDK_OUT=./obj

Previous answer (applicable in any case):

How I solve it. Not really elegant but at least it works.

Because my building mechanism is quite complicated so I had a couple of custom gradle tasks and scripts too, it doesn't really matter to me the single command for the build.

So I kept build command as is

<my_ndk_path>/ndk-build -C <my_project_path>/Android/app/src/main/

Add a the folder creation (-p don't generate error if it exists)

mkdir -p <my_project_path>/Android/app/src/main/jniLibs/

Then I move the .so files to the final location with the sync command.

rsync -avh --remove-source-files                        \
      <my_project_path>/Android/app/src/main/libs/*     \
      <my_project_path>/Android/app/src/main/jniLibs/

You can do something similar for the obj folder. I just modified my .gitignore so I left it as is.

于 2015-08-21T08:46:14.940 回答
0

The simpliest way is linking Android.mk file to Gradle, like this:

android {
    ...
    externalNativeBuild {
        ndkBuild {
            path file('src/main/jni/Android.mk')
        }
    }
}

Then just click on Sync Now and build the project

于 2021-01-08T19:32:11.483 回答