[GitHub] [incubator-mxnet] iblis17 commented on issue #18463: julia/deps/build.jl automatically downloads non-ASF binary build
iblis17 commented on issue #18463: URL: https://github.com/apache/incubator-mxnet/issues/18463#issuecomment-638235390 Hi @leezu, > Would you like to look into having either of them? Sure. I'm going to survey the new artifact system in Julia 1.3+. About the CUDA build in Python, could you show more details about the releasing process done by third-party? And I'm not sure what is this about: " ... need to be properly labeled as per Apache Software Foundation Trademark policy" This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-mxnet] iblis17 commented on issue #18463: julia/deps/build.jl automatically downloads non-ASF binary build
iblis17 commented on issue #18463: URL: https://github.com/apache/incubator-mxnet/issues/18463#issuecomment-637620259 well, IIRC that code exists in the era of early stage of MXNet.jl. I think there are two ways to provide a binary release and replace the current code 1. Just download stuff from PyPI, unpack and get the `libmxnet.so`, maybe some hacks are needed for Julia. 2. Introduce [BinaryBuild.jl](https://github.com/JuliaPackaging/BinaryBuilder.jl) to build and release binary. Here is a Julia blog post about the binary package system: https://julialang.org/blog/2019/11/artifacts/. But I never tried this approach before, there are some details needed to be figured out. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
