Johan Euphrosine

> I don't think that will help as we need to have the tcl interpreter object in c++ in order to register our swig wrapper on it. Ah yes, you're...

another thing to consider could be to have something similar to http://yowasp.org/ (OpenROAD compiled as a WASM bundle using https://github.com/WebAssembly/wasi-sdk) to enable cross platform distribute on PyPI.

To go back to my original issue https://github.com/The-OpenROAD-Project/OpenROAD/issues/1424#issue-1079742993, I'm just suggesting that we support importing the current python binding outside of the python interpreter embedded in the openroad process (`from...

Looks like https://cibuildwheel.readthedocs.io/en/stable/ can also help achieve this.

And https://github.com/marketplace/actions/pypi-publish for publishing.

Both are being maintained under @pypa so should be future safe to depends on.

The @pypa action does seems to have additional knobs to target different PyPI repository (ex: test PyPI) and run twine check to verify the package metadata before uploading. Maybe it...

> Since building is out of scope of pypi-publish, pyTooling might need to be enhanced with e.g. manylinux before using pypi-publish (or specific options of twine). It seems that @pypa...

Let's move the meta discussion to https://github.com/pyTooling/Actions/issues/47 and keep this issue about the specifics of the OpenROAD implementation of building wheels and publishing them to PyPI.

A bit more background: The goal of https://github.com/The-OpenROAD-Project/OpenROAD/pull/1849, is to expose a subset of the OpenROAD C++ API as a regular [python extension](https://docs.python.org/3/extending/extending.html), and not really to replace the main...