I can recall that we had quite a few issues where people tried to use amalgamation. Have we identified these use cases so far and documented the alternative.
I think the compilation only takes a few seconds and I think we also have some nightly tests for it. So far it seemed very low maintenance, so I'd lean towards keeping it. But if there's literally nobody using it and it's no longer useful, I'm happy to see it removed. Do we have some data on amalgamation usage? -Marco Chris Olivier <cjolivie...@gmail.com> schrieb am Sa., 7. Sep. 2019, 00:56: > Hi Pedro, > > While I was not involved with amalgamation or its development in any way, > can you please refrain from referring to the work of others as a "hacky > solution"? This is derogatory slang and the statement was not supported > with any justification for such name-calling. Someone spent a good deal of > time on this solution at some point in time and I am sure it worked for its > purpose at that time -- I think it was used in the original javascript port > as well, actually -- and it is disrespectful to call their efforts > "hacky". Please respect what came before. > > Thanks for understanding, > > -Chris > > > On Fri, Sep 6, 2019 at 3:07 PM Pedro Larroy <pedro.larroy.li...@gmail.com> > wrote: > > > Hi > > > > I would like to propose to remove amalgamation from MXNet and CI, users > > have reported that they couldn't use it successfully in Android, and > > instead they were able to use the cross compiled docker build > successfully. > > > > Any reason why we shouldn't remove this hacky solution? > > > > Pedro. > > >
