Release gdnative includes along with wrapper lib ?

[touilleMan]

@akien-mga I'm thinking maybe we distribute the wrapper lib stuff as a tarball with the static library on one hand along with the modules/gdnative/include folder. The idea would be to be totally independent from the godot repository when building 3rd party lib and avoid easy mistake like compiling with the master version of the includes and linking with the stable version of the wrapper static lib.

I see two way to do this:

• generate the tar for each platform and upload it in the github release section
• generate the tar by hand at release time. This is obviously more work, but it allow to put in the tar all the version of the static library, so a godot release would be godot binary + release templates tar + gdnative wrapper tar which seems nicer than one gdnative wrapper tar per platform.

What do you think ?

[akien-mga]

I'll go with the second option I think, I already have to do some post-processing of the CI binaries from our server to properly name them, pack the Android, JS, iOS and OSX files as expected, etc. So adding a few lines to my script to generate a gdnative wrapper zip shouldn't be hard.

What should be the names of the various static libs? Should I keep the default ones, or should I rename them to feature the Godot version (or GDNative api version?).

CC @karroffel

[karroffel]

That's what GodotNativeTools/godot_headers is meant for: manually updated headers. We could distribute them on the official download page, but my intention was to have the official and semi-official "binary devkits" in one org with some repos.