mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Skalicky <notificati...@github.com>
Subject Re: [apache/incubator-mxnet] [RFC] MXNet external operators (#18904)
Date Tue, 25 Aug 2020 04:17:48 GMT
@kpuatamazon I had a followup idea, I moved all the library specific build stuff into a **CMakeLists.txt**
in the **example/extensions/lib_external_ops** directory. So now all of your library-specific
build "stuff" is there and not in the main MXNet **CMakeLists.txt**. In this way, building
a custom library does not require changing the main MXNet **CMakeLists.txt**, instead only
the small/specific one for your custom library. 

The main MXNet **CMakeLists.txt** just refers to the one in the **lib_external_ops** directory:
https://github.com/apache/incubator-mxnet/pull/18904/files#diff-af3b638bc2a3e6c650974192a53c7291R709

You still have to build MXNet, and then use MXNet's **CMakeLists.txt** to generate the Makefile
for your custom library. But at least now the control is completely on the custom library.
You can clone MXNet, build it, delete all the example files in **example/extensions/lib_external_ops**,
drop in all of your files in the same directory, and build just the "external_lib" target.


-- 
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-679581093
Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message