Using android-gradle and maven, is there a clean way to link two native libraries when one depends on...
I have a Gradle project that publishes an Android library to my maven server (I will refer this as project A). The library is packaged as an .aar, but only contains native .so files. The structure looks like this:
libraryA.aar
|
+-- jni
| |
| +-- arm64-v8a
| | |
| | +-- native_lib_A.so
| |
| +-- armeabi-v7a
| | |
| | +-- native_lib_A.so
...etc
Now I have another Android project that builds a different native C/C++ library (I will refer this as project B). B depends on the library A.
From project B's build.gradle, I can easily pull library A from my maven server like this:
dependencies {
implementation 'com.example:libraryA:1.0.0'
}
However, I can't find any simple clean way to link the .so files from the prebuilt library A with the library B.
The best that I can do is write a messy Gradle task to unzip the aar and copy the .so files to another location that library B's make file (or CmakeList) can use. I also had to write a messy Gradle task in project A to stuff the header files into the aar in some non-standard location so that project B could use them.
So, I would like to know if there is a better way to resolve Android native dependencies when one native library depends on another pre-built native library that is packaged as an .aar and published on a Maven server?
android android-gradle
add a comment |
I have a Gradle project that publishes an Android library to my maven server (I will refer this as project A). The library is packaged as an .aar, but only contains native .so files. The structure looks like this:
libraryA.aar
|
+-- jni
| |
| +-- arm64-v8a
| | |
| | +-- native_lib_A.so
| |
| +-- armeabi-v7a
| | |
| | +-- native_lib_A.so
...etc
Now I have another Android project that builds a different native C/C++ library (I will refer this as project B). B depends on the library A.
From project B's build.gradle, I can easily pull library A from my maven server like this:
dependencies {
implementation 'com.example:libraryA:1.0.0'
}
However, I can't find any simple clean way to link the .so files from the prebuilt library A with the library B.
The best that I can do is write a messy Gradle task to unzip the aar and copy the .so files to another location that library B's make file (or CmakeList) can use. I also had to write a messy Gradle task in project A to stuff the header files into the aar in some non-standard location so that project B could use them.
So, I would like to know if there is a better way to resolve Android native dependencies when one native library depends on another pre-built native library that is packaged as an .aar and published on a Maven server?
android android-gradle
add a comment |
I have a Gradle project that publishes an Android library to my maven server (I will refer this as project A). The library is packaged as an .aar, but only contains native .so files. The structure looks like this:
libraryA.aar
|
+-- jni
| |
| +-- arm64-v8a
| | |
| | +-- native_lib_A.so
| |
| +-- armeabi-v7a
| | |
| | +-- native_lib_A.so
...etc
Now I have another Android project that builds a different native C/C++ library (I will refer this as project B). B depends on the library A.
From project B's build.gradle, I can easily pull library A from my maven server like this:
dependencies {
implementation 'com.example:libraryA:1.0.0'
}
However, I can't find any simple clean way to link the .so files from the prebuilt library A with the library B.
The best that I can do is write a messy Gradle task to unzip the aar and copy the .so files to another location that library B's make file (or CmakeList) can use. I also had to write a messy Gradle task in project A to stuff the header files into the aar in some non-standard location so that project B could use them.
So, I would like to know if there is a better way to resolve Android native dependencies when one native library depends on another pre-built native library that is packaged as an .aar and published on a Maven server?
android android-gradle
I have a Gradle project that publishes an Android library to my maven server (I will refer this as project A). The library is packaged as an .aar, but only contains native .so files. The structure looks like this:
libraryA.aar
|
+-- jni
| |
| +-- arm64-v8a
| | |
| | +-- native_lib_A.so
| |
| +-- armeabi-v7a
| | |
| | +-- native_lib_A.so
...etc
Now I have another Android project that builds a different native C/C++ library (I will refer this as project B). B depends on the library A.
From project B's build.gradle, I can easily pull library A from my maven server like this:
dependencies {
implementation 'com.example:libraryA:1.0.0'
}
However, I can't find any simple clean way to link the .so files from the prebuilt library A with the library B.
The best that I can do is write a messy Gradle task to unzip the aar and copy the .so files to another location that library B's make file (or CmakeList) can use. I also had to write a messy Gradle task in project A to stuff the header files into the aar in some non-standard location so that project B could use them.
So, I would like to know if there is a better way to resolve Android native dependencies when one native library depends on another pre-built native library that is packaged as an .aar and published on a Maven server?
android android-gradle
android android-gradle
asked Nov 13 '18 at 1:27
Tara E.Tara E.
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272459%2fusing-android-gradle-and-maven-is-there-a-clean-way-to-link-two-native-librarie%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272459%2fusing-android-gradle-and-maven-is-there-a-clean-way-to-link-two-native-librarie%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown