Hi, instead of JNA, I would be happy to provide bindings for the C API and
maintain packages based on the JavaCPP Presets here:
https://github.com/bytedeco/javacpp-presets/tree/master/mxnet
JavaCPP adds no overhead, unlike JNA, and is often faster than manually written
JNI. Plus JavaCPP provides
> @saudet Thanks for your proposal. I have four questions would like to ask you:
>
> 1. If we adopt JavaCpp package, how will that be consumed? Under byteco or
> apache MXNet? Essentially from our previous discussion, we really don't want
> another 3rdparty checkin.
We can go either way, but I
> ## What's missing
>
> javacpp-presets-mxnet doesn't expose APIs form nnvm/c_api.h (some of current
> python/gluon API depends on APIs in nnvm/c_api.h)
I've added that the other day, thanks to @frankfliu for pointing this out:
https://github.com/bytedeco/javacpp-presets/commit/976e6f7d307b3f38
> We are looking for a robust solution for MXNet Java developers to use
> especially owned and maintained by the Apache MXNet's community. I will be
> more than happy to see if you would like to contribute the source code that
> generate MXNet JavaCpp package to this repo. So we can own the main
