This is very confusing while I started reading the TVM source code, trying to figure out the build paths.
Normal build flow seems using **tvm/python/tvm/relay/build_module.py**, which itself is a wrapper for C++ implementations under the hood, such as **tvm/src/relay/backend/build_module.cc** and **tvm/src/relay/backend/compile_engine.cc**. However, I just realized VTA build has its own path from **tvm/python/tvm/driver/build_module.py**. This interface calls into **tvm/vta/python/vta/...** python files. VTA bulid is drastically different from main TVM modules. Why can't it use the standard build path? --- [Visit Topic](https://discuss.tvm.ai/t/why-does-vta-build-has-its-own-path/6259/1) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/e0757de87fa5de4ca6a8d5a8b5233828d737e83fc04300a86bdcd760e0b93bc4).
