-
Notifications
You must be signed in to change notification settings - Fork 239
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
Linking error when using cibuildwheel to build a swig based library #1890
Comments
Is this with scikit-build-core, or the classic scikit-build? Also, I see a warning about 64bit vs. 32bit, is this just on the 32bit Windows builds? |
I'm using scikit-build-core and x64 windows |
I had this problem running locally (I wasn't using scikit, but the error was very similar). Using it on GHA always works. Since I was using Python 64 it should search for the 64 libraries, but it doesn't.... |
I’ll try to look into this a bit, but I think it will Just Work™️ in the next cibuildwheel release, because we know always set that variable. But I can see if scikit-build-core can do anything to improve. |
Hey, just dropping by to say I suffered from the same issue when trying to publish my package here, but the workflow used was using v2.18, upgrading to v2.20 did indeed fix it. While it's not the exact same error as the original issue, it was still a linker issue with two symbols in our case which is fixed w/ v2.20 here 🙂 |
Description
When building a python wheel for a C++ library using swig, scikit-build and cibuildwheel, I get errors when it tries to link python C API:
Using pipx run build innstead of cibuildwheel works fine, so it seems that CMake is not able to find python's C API headers.
Is there a way to configure cibuildwheel so it exposes those headers?
Build log
No response
CI config
No response
The text was updated successfully, but these errors were encountered: