hi @areusch,
Thanks for the reply! We dont have a strict requirement per se to generate a c-source module. In fact, even if we did it would be the same source -- just binary artifacts being different. That sounds to me like we could go with O1 ? Anyhow, micro-specific or not, why do you think passing the fcompile function to the export library is not a good idea ? (Im assuming you are thinking non-uTVM use case). I think its better to provide this capability to the user either way while having a default to what it is in the export_library interface. I think we should be able to serialize the binary artifacts using the SaveToBinary interface. Therefore, the archive creation would encapsulate everything. Please let me know if Im missing something that blocks this kind of behavior in uTVM. cc : @comaniac --- [Visit Topic](https://discuss.tvm.apache.org/t/external-modules-in-utvm/7993/3) 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/5ff66c73eff47edbd066e8208ebea5f381553eab3a040f9e7db1c6cf031705c8).
