Ahmed S. Taei

@garymm yes, you can write bazel rules for each cmake library easily with very little manual effort one caveat there is a small header circular dependency between `Troch\Transforms\* && TorchConversion\`...

> > @garymm yes, you can write bazel rules for each cmake library easily with very little manual effort one caveat there is a small header circular dependency between `Troch\Transforms\*...

> > There is another small caveat here, bazel can't have a top level directory [external](https://github.com/bazelbuild/bazel/issues/4508), it works on my case because torch_mlir is dependency and not the main repo...

I send a #706 for rules to build the compiler part, I will send followup PRs for python bindings and lit tests.