Another key advantage of this design will be a broader support on
> > > different implementations such as Java Cpp. User will be able to
> > implement
> > > their customized MXNet frontend to use the native library.
> > >
> > > Thanks,
> > > Qing
> > >
> > >
rary.
> >
> > Thanks,
> > Qing
> >
> > ____________
> > From: Sheng Zha
> > Sent: Tuesday, July 2, 2019 22:14
> > To: dev@mxnet.incubator.apache.org
> > Subject: Re: [DISCUSS] Make MXNet deploy it's own distribution
> >
> > Does i
> > >
> > > Another key advantage of this design will be a broader support on
> > > different implementations such as Java Cpp. User will be able to
> > implement
> > > their customized MXNet frontend to use the native library.
> > >
> > > Thanks,
t; different implementations such as Java Cpp. User will be able to
> implement
> > their customized MXNet frontend to use the native library.
> >
> > Thanks,
> > Qing
> >
> > ____________
> > From: Sheng Zha
> > Sent: Tu
gt; Qing
> >
> > ________
> > From: Sheng Zha
> > Sent: Tuesday, July 2, 2019 22:14
> > To: dev@mxnet.incubator.apache.org
> > Subject: Re: [DISCUSS] Make MXNet deploy it's own distribution
> >
> > Does it mean that the scala bi
mplementations such as Java Cpp. User will be able to implement
> their customized MXNet frontend to use the native library.
>
> Thanks,
> Qing
>
>
> From: Sheng Zha
> Sent: Tuesday, July 2, 2019 22:14
> To: dev@mxnet.incubator.apac
: [DISCUSS] Make MXNet deploy it's own distribution
Does it mean that the scala binding of mxnet will be an independent package
that doesn’t directly depend on the native package, and user projects need to
declare dependency on both the scala binding and one of the native packages?
-sz
> On Ju
Does it mean that the scala binding of mxnet will be an independent package
that doesn’t directly depend on the native package, and user projects need to
declare dependency on both the scala binding and one of the native packages?
-sz
> On Jul 2, 2019, at 5:50 PM, Frank Liu wrote:
>
>
