> How about components in general? Let's say we would like to externalize the > onnx support or some other component? We would still always have to build > these things together and specify the features set during compile time, right?
It depends on what "externalize the onnx support" entails. Today the only components we register are: operators, subgraph properties, and graph passes (anything else?). The current onnx support is implemented [entirely in Python](https://github.com/apache/incubator-mxnet/tree/master/python/mxnet/contrib/onnx). Maybe we could externalize TensorRT as a custom subgraph property & custom op though. You dont need to build them together as much as you need to reproduce the same build settings (defines, includes, etc). The big reason that you cant just compile your code and link against libmxnet.so is the same as why you cant build a custom application using the C++ API without compiling it with MXNet: it depends on the entire codebase (+3rd party submodules). -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/pull/18904#issuecomment-679737968
