## Motivation
Currently `tvmc` will only produce a dynamic library version of the network, i.e., an `.so` file stored alongside the other artifacts. This library is usually dynamically linked to other applications. With this change we want to add a flag to `tvmc` to get an object file (i.e., with a `.o` extension) as well as the dynamic library, to statically link against the target applications. This will be very useful for bare-metal targets that cannot link against dynamic libraries. ## Summary of the change **Standard behavior:** `tvmc compile mynetwork.tflite` → `mod.params`, `mod.so`, `mod.json` **Enhanced behavior:** `tvmc compile --flag-name mynetwork.tflite` → `mod.params`, `mod.so`, **`mod.o`** , `mod.json` ## Possible names for the tvmc flag Here is a list of possible flag names: * `--bare-metal` * `--object-file` * `--static` Feel free to add more, and let's agree on one in particular --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-optionally-include-object-file-generation-in-tvmc/8120/1) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/7afe350d548761d97e0efc5ead584458b98e69375792123caab6fdc587fea0eb).
