-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package swig bindings as shared libraries #2308
Comments
@proppy I have a demo working for one of them |
The .a are used to build a statically linked binary which is much simpler for users as it doesn't require setting up an LD_LIBRARY_PATH entry. |
@maliberty understood, but curious if there a usecase for having the swig bindings |
openroad -python needs the swig bindings and is statically linked. |
@proppy We need to set up the infrastructure to build and package the so's for pip. |
@macd FYI |
It would be nice to be able to import into an unmodified Python. I will take a look at @QuantamHD changes (I have PoC wrappers for about 10 of the tools/libs at present). How many versions of Python do you envision building against? |
In order to be able to import them from
.py
script, the swig binding needs to be built as shared libraries.Currently the
swig_library
helper forces static linking, see:https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/src/cmake/swig_lib.cmake#L74
@maliberty is the
.a
actually needed by something else in the build? do we need to build both or can we get away with only building the.so
?/cc @QuantamHD
The text was updated successfully, but these errors were encountered: