Establishing a home for TVM dev tools

Development RFC
7

We discussed this at the Community Meeting today. Here are notes:

  • @leandron: docker/build.sh → dev/docker-build.sh
    • Can consider combining with docker-run.sh (i.e. add a flag)
  • @leandron: Where do Dockerfiles live?
    • Maybe makes sense to keep them close to bash.sh and `build.sh in the same dir—simplifies those scripts.
    • @areusch: Would rather keep those in ci rather than dev.
    • @leandron: important thing is to keep the install dir needs to stay relative to Dockerfile
    • You could cast these as dev tools if someone was installing deps on their local machine outside the Dockerfiles.
    • It’s challenging to take a libtvm_runtime.so built inside a Docker container and run it elsewhere.
  • @Gromero: what’s the official recommended path to start developing for microTVM?
    • @areusch: Reference VM if hardware is in the loop. Otherwise, docker images (moving towards 1-image-per-arch.
  • @areusch: does this influence folks’ workflow on the call?