> From the usability point of view, JavaCPP will also offer similar > funcionalities. @saudet will you be open to consider if MXNet JavaCPP can be > fully donated to Apache MXNet and maintained by community?
Yes, that's what I'm offering. I would sign up as a contributor to make an initial contribution and also do what needs to be done to get it working for your purposes. > These two solution is very similar and potentially JavaCPP can bring some > level of performance improvement. My only concern to JavaCPP is @szha initial > question, how we are going to build/maintain the Java package. I'm sorry, I must have missed that question, and I'm not sure I see it above. Can you point it out just to be sure? I've since released a Gradle plugin, and I think that answers the question though. Here is an example that builds and packages bindings for zlib: * https://github.com/bytedeco/gradle-javacpp/tree/master/samples/zlib Just pop that in a script for GitHub Actions and what not and it works. The build.sh script does not need to build the libraries from scratch either. It can be modified to download and extract existing binaries, for example, like it's doing in the case of MKLML here: * https://github.com/bytedeco/javacpp-presets/blob/master/mkl-dnn/cppbuild.sh#L28 Does this look satisfactory? -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/17783#issuecomment-701148359
