It's optional for MXNet to use ZeroMQ. Even if it is enabled, the source codes of MXNet will not contain any codes from ZeroMQ except for "include<zmq.h>" and calling zeromq's APIs. But if we want to ship the binary, it will link against libzeromq.a
On Thu, Jul 6, 2017 at 9:21 AM, John D. Ament <johndam...@apache.org> wrote: > Hen, > > Can you give some more info about how MXnet uses ZeroMQ? Is it an optional > dependency or required? Are you actually bundling ZeroMQ in your release > (source or binary)? > > John > > On Thu, Jul 6, 2017 at 2:23 AM Henri Yandell <bay...@apache.org> wrote: > > > One of the items that is on the list to do before releasing Apache MXNet > is > > removing ZeroMQ from the codebase/dependencies. > > > > ZeroMQ is licensed under the LGPL 3.0 with an exception for static > > compiling. > > > > They have long been interested in relicensing to MPL 2.0, but haven't > made > > much progress, though they did relicense JeroMQ (Java > > wrapper/implementaiton) last year. > > > > In the last few months they've made a lot of progress towards > relicensing: > > https://github.com/zeromq/libzmq/tree/master/RELICENSE > > > > I'd like to ask on legal-discuss@ for an exception (one year?) to > continue > > using ZeroMQ, with prominent documentation, in MXNet given the trend > > towards MPL 2.0. > > > > Any concerns before I do so? > > > > Thanks, > > > > Hen > > >
