search

mahmud83 / maven-android-plugin

Automatically exported from code.google.com/p/maven-android-plugin
0 stars 0 forks source link

Multiple NDK architectures not present in APK, mvn 3.1.1, plugin 3.8.2. #445

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Make a pom.xml with a native library xxx.  Add two architectures:

          <ndkArchitectures>armeabi armeabi-v7a</ndkArchitectures>

2. mvn package

What is the expected output?

An APK with lib/armeabi-v7a/xxx.so and lib/armeabi/xxx.so

What do you see instead?

APK only contains lib/armeabi-v7a/xxx.so.

Also, the directory where the build is done only has libs/armeabi-v7a/xxx.so,
libs/armeabi/xxx.so is missing here too.

What version of maven-android-plugin are you using?

3.8.2.

What are the complete output lines of "mvn -version" on your machine?

Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 
17:22:22+0200)
Maven home: /usr/local/apache-maven
Java version: 1.6.0_65, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: sv_SE, platform encoding: MacRoman
OS name: "mac os x", version: "10.9.1", arch: "x86_64", family: "mac"

Please provide any additional information below.

The output from the build suggests armeabi is build, and it is in the obj/ 
directory:

[INFO] --- android-maven-plugin:3.8.2:ndk-build (default) @ BlaAndroid ---
[INFO] executing 8 parallel jobs
[INFO] /Users/xxx/android-ndk-current/ndk-build [-C, /Users/xx/1.3.44, -j, 8, 
NDK_TOOLCHAIN=arm-linux-androideabi-4.6, APP_ABI=armeabi, xxx]
[INFO] Cleaning up extracted include directories used for build
[INFO] executing 8 parallel jobs
[INFO] /Users/xxx/android-ndk-current/ndk-build [-C, /Users/xxx/1.3.44, -j, 8, 
NDK_TOOLCHAIN=arm-linux-androideabi-4.6, APP_ABI=armeabi-v7a, xxx]
[INFO] Cleaning up extracted include directories used for build

Workaround is to set target to:

 <target>APP_ABI=armeabi armeabi-v7a</target>

I don't understand the reason for this plugin to mess with APP_ABI at all, the 
info is in the Application.mk file already.  Ditto NDK_TOOLCHAIN and target.  A 
way to specify that a plain ndk-build without any arguments should be run would 
be appreciated.  Or a way to say that no APP_ABI and/or no NDK_TOOLCHAIN and/or 
no target should be passed to ndk-build.

Original issue reported on code.google.com by jhdi...@gmail.com on 12 Feb 2014 at 10:54

GoogleCodeExporter commented 9 years ago 
Having the same issue with 3.8.2.

Original comment by andrey.c...@gmail.com on 25 Feb 2014 at 9:21

GoogleCodeExporter commented 9 years ago 
Is this still a problem with 3.9.0-SNAPSHOT?

Original comment by malac...@gmail.com on 28 Mar 2014 at 7:42

GoogleCodeExporter commented 9 years ago 
I don't know how to access 3.9.0-SNAPSHOT

Original comment by jhdi...@gmail.com on 28 Mar 2014 at 5:36

GoogleCodeExporter commented 9 years ago 
Easiest way is to checkout the project and build it yourself. 5 mins work.
And since you've checked out the source you can now contribute too -
everyone wins :-)

Original comment by william....@xandar.com.au on 28 Mar 2014 at 11:04

GoogleCodeExporter commented 9 years ago 
Still an issue with 3.9.0-SNAPSHOT.
Still only compiles for the last architecture in <ndkArchitectures>

Original comment by jhdi...@gmail.com on 29 Mar 2014 at 3:08

GoogleCodeExporter commented 9 years ago 
We are no longer using the issue tracking system on Google Code. Please refile 
this issue on https://github.com/jayway/maven-android-plugin/issues if you 
still have this problem with the latest release of the Android Maven Plugin

Original comment by mosa...@gmail.com on 19 May 2014 at 4:20