| Issue |
56037
|
| Summary |
[mlir python] Dis-aggregating MLIRPythonExtension.Core
|
| Labels |
mlir:python
|
| Assignees |
|
| Reporter |
mikeurbach
|
Since the work last year to refactor how MLIR Python extensions are linked, we have had this comment about dis-aggregating MLIRPythonExtension.Core: https://github.com/llvm/llvm-project/blob/6ccc2733e72017999a94c10147a71ff595286080/mlir/python/CMakeLists.txt#L279
My understanding is this dependency on MLIRCAPIRegistration is pulling in all the MLIR dialects, translations, and conversions: https://github.com/llvm/llvm-project/blob/10affe74eddb32bd36524e0e42310ef49aadaa3f/mlir/lib/CAPI/Registration/CMakeLists.txt#L1-L14
Some downstream projects may not want all of that, and may just want to depend on the "core" MLIR Python extension. This is definitely the case in the CIRCT project.
I wanted to open an issue before diving in to see if anyone has thoughts about how to go about this.
cc @stellaraccident
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
