that is right, in such case, we will need to ensure downstream project structured to depend on the same libtvm. So both projectA, and projectB depends on the same upstream TVM (via include dependency), but also build new optimization transformations on-top.
That does mean we need to restructure the projects instead of simply doing inplace modification, for example, MLC LLM add customized pass and runtime function on top while taking tvm as a dependency. Our hope is that by updating the upstream APIs to be more modular, such transformations can happen more organically. --- [Visit Topic](https://discuss.tvm.apache.org/t/phasing-out-legacy-components/17703/5) 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/ec13e4a3b50896ede0c9539ac61119575d5973a7c516fd92b832b24f2f44bfcd).
