Oculus mobile godot plugin v2 #71
Conversation
m4gr3d
force-pushed
the
oculus_mobile_godot_plugin_v1
branch
4 times, most recently
from
845ebe2 to
9517b92
Compare
m4gr3d
force-pushed
the
oculus_mobile_godot_plugin_v1
branch
2 times, most recently
from
b6acee2 to
09203c9
Compare
There was a problem hiding this comment.
I really like we're completely baseing this on gradle now, it seems like we're simplifying the build system for Android.
Once the upstream PR gets merged, mind having a look at the examples on the GDNative repo and adding the code to compile the basic examples on Android for that so people can see it works this way?
…n architecture. This transforms the original project into an Android library project, which has the nice side effect of simplifying integration with Android Studio and gradle.
In the process, we update the build dependencies to include a `compileOnly` dependency on the godot library aar file as it will be provided at runtime by the host Godot apk.
…hared libs, plugin binary).
… from project source code.
These will be used by the nativescript and jni accessors to provide the plugin functionality to their respective environments.
m4gr3d
force-pushed
the
oculus_mobile_godot_plugin_v1
branch
from
09203c9 to
7cad2db
Compare
m4gr3d
changed the title
m4gr3d
changed the title
|
@NeoSpark314 @BastiaanOlij I've created a |
@BastiaanOlij Can you point me to the examples on the GDNative repo. |
Probably getting |
Refactor of the Oculus mobile plugin to match the newly proposed Godot Android plugin architecture (PR godotengine/godot#33682).
In addition:
Note: This is still a WIP with numerous missing parts (including updated documentation). I'm putting it early for review to start the conversation about the new architecture.