building for android fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, cmake, java, unity
- Domain
- build-system, mobile-dev
Research direction
Start by comparing the build instructions and local.properties settings in the liblsl-Android and liblsl-Java repositories, then reproduce the failure with Android Studio and command-line Gradle using the reported SDK, NDK, CMake, and Java versions. Determine which prerequisite or configuration causes the ExternalSystemException and document whether the Android build produces an .aar or .so suitable for the Unity application.
Written by the indexing model from the issue text.
Description
Hi All
I'm trying to build LSL for android to be able to use it in a Unity VR app (android device).
I'm assuming I need an .aar or .so file within my unity environment to be able to build a VR app for android.
I'm posting this in the 'main' repo as I have the issue in both liblsl-Android as well as liblsl-Java.
I've tested this issue on multiple devices as well as Ubuntu 22.04 and Windows 10.
When I try to build via Android studio as well as via command line gradle, I encounter the next message:
com.intellij.openapi.externalSystem.model.ExternalSystemException (no error message)
Which isn't really helpful :)
I've adapted my local.properties file so it targets:
android SDK & Ndk (ndk version 21.0.6113669)
cmake 3.22.1
java 11.0.16
Are there some prerequisites missing from the instructions to be able to build?
Am I correct assuming that I need the .aar or .so file to use from unity to an android device?
Sincerely
Wouter
- Dominant language
- HTML
- Stars
- 778
- Forks
- 194
- Avg merge
- 13m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sccn/labstreaminglayer
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sccn/labstreaminglayer#138 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
sccn/labstreaminglayer#134 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
sccn/labstreaminglayer#131 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
sccn/labstreaminglayer#130 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
sccn/labstreaminglayer#127 · 6 comments ·
All issues in sccn/labstreaminglayer
Similar issues
-
Needs Design Priority: Wishlist
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
elementary/flatpak-platform#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/hone-maven-plugin#1060 ·
-
0.kind: build failure
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100