aghilasmessara / android-native-dependencies Goto Github PK

Any suggestions on how to approach this problem? http://stackoverflow.com/questions/24314983/how-to-exclude-duplicate-c-shared-libraries-so-in-a-multi-project-android-bui/26079631

I find the .so files less than that the maven downloaded. can this plugin handle transitive dependencies?

Hi, your android-native-dependencies is great. Thanks for sharing.
I have found that in copyToTarget you use the directory:
"$project.projectDir"+File.separator+
"src"+File.separator+"main"+File.separator+
"jniLibs"+File.separator+"$architecture"
However, if i change the android sourceset, that is not right, you may use jniLibs.srcDirs which is better.

Will you add support for arm64-v8a?

If a native dep is not found, it should fail the build - or more preferable, have a flag to specify whether to fail on missing dependencies.

Hi,

Great plugin!

I found that when libs are copied to the jniLibs directory, the .so file names are appended with "lib". So if the file name was originally "test.so", it becomes "libtest.so".

This is leading to linkage problems. Is there any reason you need to append "lib" to the filenames?

Thanks!

If we only upload and replace .so files with new ones, but not change to a new version, the android-native-dependencies won't update the files until I remove the cache files from ~/.gradle/caches.

Plugin is broken for Gradle 7.0 because pf property annotation

Some problems were found with the configuration of task ':PnRGateService:resolveNativeDependencies' (type 'NativeDependenciesResolverTask').

• Type 'com.nabilhachicha.nativedependencies.task.NativeDependenciesResolverTask' property 'ARM64_FILTER' is missing an input or output annotation.

  Reason: A property without annotation isn't considered during up-to-date checking.

  Possible solutions:

  1. Add an input or output annotation.
  2. Mark it as @internal.

Is this plugin still maintained? If I have a pull request will it be merged?

I get in two machines (dev and build server):

Build failed :|
Unable to initialize project data from Gradle build file:

A problem occurred evaluating project ':com.nutiteq.advancedmap3'.
> com/nabilhachicha/nativedependencies/NativeDependenciesPlugin : Unsupported major.minor version 52.0

Same works in another machine (with Java 1.8). Perhaps the machines have older JDK, and your build is with newer JDK? Can you make the plugin to work even if developer has older Java versions?

Such as:

native_dependences {
  debugArtifact 'artifact1'
  releaseArtifact 'artifact2'
  artifact 'artifact3'
}

The artifacts could be copied into jniLibs of the corresponding buildType. (e.g. src/debug/jniLibs)

I got a PR almost ready that allows to do debug_native_dependencies and release_native_dependencies but that doesn't seem ideal.

Perhaps even compile jniLib('artifact') so we can use debugCompile jniLib('artifact')