@PONO You’re partly correct. In this case the challenge is more around the fact that our configuration needs to be suitable for use on shared classroom computers, so for us default paths need to be changed away from the normal user profile locations. We also wanted to avoid using Oracle Java due to their punitive licensing arrangements, so in my case I chose the Microsoft OpenJDK (as we’re mainly a Windows organisation, so I figure the Microsoft one will have best compatibility with our environment).
Regardless of this I wouldn’t have got this far without @antinnit ‘s helpful guide, so I’m grateful for that. Now I just need to improve our setup process so we can mass deploy to a classroom of computers.
Hello, I followed the steps and now I am trying to make a build: “**Build Quest APK”
**
However, when I click Platforms → Android → Package Project, it tells me:
”The SDK for Android is not installed properly, which is needed to generate data. Check the SDK section of the Launch On menu in the main toolbar to update SDK.”
In Project Settings, I have correctly setup paths to SDK, NDK, Java, and set the SDK and NDK api level.
I’m not familiar with your full environment, but this method worked for me using Microsoft OpenJDK. I also structured it around environment variable paths to make it easier to reproduce consistently across a lab setup.
@antinnit yes this is exactly what I did (except in a command line manner so I can do mass deployment).
Another wrinkle: putting the Meta plugins into the project folder is not just recommended, it is required - turns out the package fails to build otherwise.
Cool, glad you’re up and running. I put the plugins in the project folder mainly for version control and to keep track of which plugin belongs to which project.
