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

[Sylvain Noiry]

ElectrikSpace wrote:

Ok thanks. I though having distinct `DECLARED_SOURCES` in `add_mlir_python_common_capi_library` for `MLIRPythonCAPI` and `MYPROJECTPythonCAPI` + dynamic linking + no duplication of any Python file would be enough (And it works on our compiler with a Transform dialect + MLIR + LLVMIR pipeline).

So if I want to build let's say `mlir_sdist`, `mlir_aie` and upstream to make them work together, if I'm correct I need to create a mega package that build everything together, and name it `mlir` to prevent the replacement of all imports using it.

> I can try revisiting that issue/PR - I don't remember the particular problems with it. If you add the description of your problem/goal there, it'll help motivate me 😄.

This was just too much cmake for me, I though working with CAPI directly would be easier.

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