gromero commented on pull request #8380: URL: https://github.com/apache/tvm/pull/8380#issuecomment-895298535
> I discussed with @areusch one small usability point that we well need to aadress later, which is basically that the template project won't be added to Python packages generated from the TVM repo _as is_. > > We'll need to offer some mechanism (and documentation) for a user to point to a Git repo and a path to access the template project to be used, or even maintaining an index of known-good repos and paths we know. This can be done via APIs or indeed via `tvmc` (cc @gromero). > > It is probably something that will confues people who are not familiar with the code base and just want to use TVM as a tool. @leandron yeah, that's a good point. I was not aware that the template dirs would be out of the currently existing TVM Python packages. How is the code in 'apps' handled currently in general? Would it make sense have another package just for the templates and add it as a dependency when on installs the other TVM packages? Or even leave the package install as optional and `tvmc` would warn the user about it being absent (not installed) - current `tvmc micro` allows two ways to specify the template dirs: 1) by project type (passing `-t zephyr` or `-t arduino`, for instance), and 2) passing a `PATH` to a template dir. Option 1. is where TVMC can detect the missing server in the default template dirs and warn the user, saying the user can install the optional package or go for using option 2., in case the template dirs are in ad hoc location. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
