mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lanking <notificati...@github.com.INVALID>
Subject Re: [apache/incubator-mxnet] [RFC] MXNet 2.0 JVM Language development (#17783)
Date Wed, 30 Sep 2020 17:18:56 GMT
@saudet Sounds good to me.

So can I say that all source code need to build will be inside Apache MXNet? We may only import
some other Java packages that are necessary to build instead of consume as submodule.

However, during MXNet 1.x, we are facing one key issue: we have to separate native binary
with Java package due to license issue. As far as I know, JavaCPP require both of them build
together, can we separate native binary with JavaCPP when we do the publish work and make
it usable for user provide their own native binary (e.g grab from pip wheel)? This requirement
typically came from GPU use cases, we have different GPU distribution for different Arch/OS
(CU101/CU102/CU110).

To make it fully usable, there will be some additional tasks for JavaCPP such as type-mapping
to form all Java object into JavaCPP pointer. Will we have similar stuff for MXNet?

-- 
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-701528247
Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message