Hi @gromero,
Thanks for the proposal.
I have a concern regarding the tvmc compile and how it should it be unified/seperated with existing flows for non-micro flows.
My view is we should be primarily be able to provide a path way to get something proposed/(eventually get agreed) as the Model Library ([µTVM] Mini-Map: the µTVM Developer Workflow)
I think firmware compilation should be seperate from tvmc compile, however its upto to debate whether we want a seperate peer to compile subcommand or an intergrated option for the compile subcommand. I think most users would want to use TVM directly embedded in the application (w/o going through a RPC server) – similiar what’s done here : ([µTVM] Static Runtime Code Generator - #2 by areusch). Thus, we would not want to tvm to create the final .hex/.elf in tvmc compile but maybe we can have tvmc compile --firmware / tvmc <someother command to indicate firmware compilation>.
I think if we agree tvmc compile is to be reserved for the creation of Model Library, then we can have alignment/unification with current tvmc target specification. What do you think?