Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ViroCore 1.18.0, ARCore 1.21.0 #346

Open
iTruff opened this issue Nov 16, 2020 · 4 comments
Open

ViroCore 1.18.0, ARCore 1.21.0 #346

iTruff opened this issue Nov 16, 2020 · 4 comments

Comments

@iTruff
Copy link

iTruff commented Nov 16, 2020

I was able to update ARCore version to 1.21.0 and build new virocore-release-v_1_18_0.aar.
See files below:

core-1.21.0.aar.zip
virocore-release-v_1_17_0.aar.zip

@hannesa2
Copy link

I want to see it on this (or any master)
How can I help to automate this ?

@iTruff
Copy link
Author

iTruff commented Nov 18, 2020

Hi @hannesa2 Unfortunately I can't make it public due to lack of time.

You can do it yourself:
How to build ViroCore
How to update ARCore version

@ebelinski
Copy link

@iTruff When I use these two AAR files, I encounter this error:

More than one file was found with OS independent path 'lib/armeabi-v7a/libarcore_sdk_c.so'. If you are using jniLibs and CMake IMPORTED targets, see https://developer.android.com/studio/preview/features#automatic_packaging_of_prebuilt_dependencies_used_by_cmake

Could it be that you uploaded the wrong AAR file for ViroCore? I noticed your text says "virocore-release-v_1_18_0.aar" but the file below is "virocore-release-v_1_17_0.aar.zip".

@iTruff
Copy link
Author

iTruff commented Jan 5, 2021

@ebelinski No, it's just a naming issue, you can fix your problem with custom packaging options in your build gradle

packagingOptions {
        pickFirst 'lib/armeabi-v7a/libarcore_sdk_c.so'
        pickFirst 'lib/arm64-v8a/libarcore_sdk_c.so'
        pickFirst 'lib/x86_64/libarcore_sdk_c.so'
}

or it's possible to exclude these files during building virocore-release-v_1_18_0.aar but i forgot to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants