Hi guys Thanks for your responses. I'm definitely interested and will have a look at the pointers provided. I did a small prototype yesterday to compile LeNet against MXNet outside the source tree and was able to get something to compile while adding libmxnet, libdmlc, nvvm includes, dmlc includes, mxnet-cpp and mxnet includes. (It also segfaulted but at least it compiled and linked)
One one hand is good that this might be sufficient for getting things to work, but also shows that the situation is not ideal if you want to use MXNet natively. There's also the additional complexity of the linked dependencies and compile time options such as opencv etc which needs to be addressed on the build file of the external project. I didn't know about the snap package and will have a look. I would like to have easily buildable artifacts for several platforms, including a deb file for ubuntu based platforms in addition to other packages such as python wheels. Right now many users spend too much time trying to compile and deploy on different platforms. Right now is still not easy to do these tasks, this should be more user and developer friendly. Pedro. On Thu, Feb 15, 2018 at 1:17 AM, Can Balioglu <cbalio...@fastmail.com> wrote: > Hi Pedro, > > Actually my team had the exact same requirement and we now have an internal > MXNet package with all the necessary header files. Note that if you have some > custom operators and plan to write an extension library for them, you are > going to need to copy not only the public header files but also the private > ones under the src directory. Unfortunately the separation of public and > private types are not well-defined and there is definitely some room for > improvement. Just let me know if you need any feedback. > > By the way I am working on writing a CMake Find-module for MXNet. In case you > are interested I can keep you posted. > > -Can > > On Wed, Feb 14, 2018, at 19:03, Anirudh wrote: >> Hi Pedro, >> >> Canonical added snap package for MXNet last year: >> https://github.com/apache/incubator-mxnet/pull/4852 >> Would be good to verify if it works for your use case. >> >> Anirudh >> >> On Wed, Feb 14, 2018 at 1:49 PM, Marco de Abreu < >> marco.g.ab...@googlemail.com> wrote: >> >> > Sounds like a great idea! Please also consider the issues labelled as Cpp >> > package on GitHub. >> > >> > -Marco >> > >> > Am 14.02.2018 6:48 nachm. schrieb "Pedro Larroy" < >> > pedro.larroy.li...@gmail.com>: >> > >> > > Hi >> > > >> > > We would like to use MXNet from C++ without Python. Currently the cpp >> > > package depends on additional MXNet headers, nnvm and dmlc. >> > > >> > > As far as I know we don't have a standalone package of MXNet with >> > > library + headers. >> > > >> > > I would like to create a deb package of MXNet for example which has >> > > the library and headers so standalone C++ applications linked against >> > > MXNet can be created. >> > > >> > > Is anybody else working on this? Any additional feedback / gotchas >> > > that I should be aware of? >> > > >> > > Pedro. >> > > >> >