[Mlir-commits] [mlir] [MLIR][Python] Extend bindings for external projects without duplication (PR #173241)

[Maksim Levental]

makslevental wrote:

> The use case for all this that I work on a project that uses MLIR Python bindings from a wheel (https://gitlab.inria.fr/CORSE/mlir-bindings-wheels), and I want to optionally use external projects (more than one) to extend it, that are installed using wheels. So I want every project to use the same `libMLIRPythonCAPI.so`, which is linked statically for now. At the end I should end up with a dependency to the mlir wheel for each external project, and it should work.

Ok but how will you "find" that lib when building/compiling/linking your "external" wheel? There's no more CMake exports at that point right?

> Except the import paths transformed from relative to absolute in `mlir-tablgen` I don't want to change how existing projects and upstream are built and linked.

I understand you don't intend to - I'm saying you have to *make sure* it doesn't negatively affect anyone else's project. 

https://github.com/llvm/llvm-project/pull/173241