Initial gradle plugin subproject

PokeMMO commented 5 years ago

Still needs a bit more work/cleanup to get it where i'd like it, but here's a good first revision.

Can we diverge from libgdx version numbers? Having this library update much more frequently for minor things and non-breaking feature change would be quite nice.

Initial publish is very barebones, but functional. ./gradlew publishToMavenLocal is enough to test for now.

MobiDevelop commented 5 years ago

I don't see any reason the version needs to match libgdx if this could benefit from a different release cycle.

PokeMMO commented 5 years ago

With the latest Android.mk/Applicaiton.mk support this should now be up to feature parity with libdgx base java based builds.

I realized I should probably ask if I should be adding new features before or after this gets merged. Things like the jnigenBuild commands which actually invoke the builds, jar packaging tasks, arm support, or clean tasks.

MobiDevelop commented 5 years ago

I'm okay with adding features. I would like @Tom-Ski to take a peek at this PR before merging.

MobiDevelop commented 5 years ago

Not sure if we're going to get a review from the great Tom-Ski here, so let me know when you want to merge.

Tom-Ski commented 5 years ago

Hey, yeah, i did a little look. But wanted to restructure some of the stuff for deployment.

PokeMMO commented 5 years ago

I'm still not quite happy with a few things:

Jar tasks (and therefore publishing) are clunky, let alone missing IOS support.
macOS only builds are clunky, jnigenBuild should prob be smarter to only run current platform compatible targets instead of requiring you to manually run IOS/MacOS tasks.
macOS makes desktop deploy clunky, because natives-desktop is a single archive. It requires you to manually figure out a mechanism to copy over macOS builds if you aren't cross compiling. (The only way I can see to maybe make this better would be to split desktop like LWJGL3's new classifiers)
Clean task for jnigen artifacts. (Deleting old no longer used javah h/cpp files seems unsafe and potentially destructive if people put their main h/cpp files in jni folder)

Things which I want to try, but probably don't belong in the initial commit:

Move c/cpp includes to proper src/main/c src/main/cpp folders by default.
Move generated build scripts from the jni folder to a proper gradle build/jni or something.
Upgrade javaparser to latest now that we're allowed to use java 8.

PokeMMO commented 5 years ago

Oh also, there's the SharedLibraryLoader subproject I want to add, but there's a limitation noted in https://github.com/MobiDevelop/gdx-jnigen/issues/2

Tom-Ski commented 4 years ago

Happy to merge as is, after we can make a repo in LibGDX and continue work from there?

PokeMMO commented 4 years ago

Sounds fine to me.

MobiDevelop commented 4 years ago

Sounds good, I'll merge then move this repo to the libgdx org later today.

libgdx / gdx-jnigen

Initial gradle plugin subproject #1