I think we should bias towards static linking. It should make using mxnet easier in a lot of cases for users. As long as the license permits static linking (i.e. is non-gpl) I'd +1 static linking for portability and ease of use. The only caveat would be in cases where the package size would cause grief for PyPi maintainers.
On Thu, Nov 8, 2018, 3:54 PM Sheng Zha <zhash...@apache.org wrote: > +1. Ideally, MKLDNN can be statically linked. mxnet-mkl relies on Make for > building it so help is wanted on mxnet. > > -sz > > On 2018/11/08 21:28:50, Alex Zai <aza...@gmail.com> wrote: > > Currently in mxnet-mkl the libmxnet.so is dynamically linked to to > > libmkldnn.so.0. This is known to cause some issues if the wrong version > of > > mkldnn is linked. Can we static link this file instead? > > > > Alex > > >
