For the deployment flow, I think we could have a cleaner flow to produce c sources or object files (I prefer this but c-sources should also be fine in-case the users need manual customization post-tvm). The intent being there artifacts could be obtained via tvmc compile, thus integrator (who integrates the app and RTOS) could use them directly in the project.
However, as @areusch points out the tuning process makes this complicated in the absense of dynamic linking in the device which runs RPC server.
Lately, we’ve been thinking could we use specialized apps as RPC servers for each of RTOS that have auxiliary interface to obtain linking information OR have a light-weight linking process to support mapping platform-specific functions in the server itself – therefore the compiler does not need generate RTOS specific projects and rely on the server to get linking info / have server does the linking. @areusch side question : do we do re-flashing in the process of tuning currently or we just handle the operator code in heap/stack ?
This could allow a cleaner compilation interface while supporting tuning.