# \[RFC\] Optionally include object file generation in tvmc

**URL:** <https://discuss.tvm.apache.org/t/rfc-optionally-include-object-file-generation-in-tvmc/8120>\
**Category:** RFC\
**Created:** [October 8, 2020, 5:50pm UTC](https://discuss.tvm.apache.org/t/rfc-optionally-include-object-file-generation-in-tvmc/8120 "2020-10-08T17:50:45Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![leandron](https://discuss.tvm.apache.org/user_avatar/discuss.tvm.apache.org/leandron/32/1205_2.png) [@leandron](https://discuss.tvm.apache.org/u/leandron)\
**Post date:** [October 9, 2020, 10:08am UTC](https://discuss.tvm.apache.org/t/rfc-optionally-include-object-file-generation-in-tvmc/8120/6 "2020-10-09T10:08:33Z")

</div>

I think the idea is good, I remember it was raised on one of the code reviews by @FrozenGene, to fulfill this use-case of users who are not interested in `tvmc run` their modules, but instead, want to get an object file to link their own apps.

The question now is how do we name optional things into `tvmc`. I like `--object-file`, but sometimes I feel we should have an action before it, like `--add-object-file` or `--enable-object-file`.

cc @comaniac that has good suggestions about naming parameters.

---

_[View the full topic](https://discuss.tvm.apache.org/t/rfc-optionally-include-object-file-generation-in-tvmc/8120)._