-
|
I'm trying to build a C extension package for some exotic architectures, and run its test suite within cibuildwheel. However, I think they are provided by the container image, and could be installed with the system package manager. Could an option be added to cibuildwheel to pass |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment · 5 replies
-
|
I think I'd probably try setting PYTHONPATH in test-environment. I'm guessing you're using a custom container image, so you probably know the exact paths where the system packages are installed. If you're building multiple versions of python, you'll need to use TOML overrides to set a different path for each python version. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the pointers, I'll give that a try. It's not actually a custom image, just cibuildwheel-managed ppc64le and s390x so far, but I should be able to figure out the paths. On the other hand, I'm already wondering if we wouldn't be better off doing something custom with cross-compilation, as emulation is so slow... |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Oh no, in fact it doesn't work. I just forgot to add the |
Beta Was this translation helpful? Give feedback.
-
|
You would need a custom testing image for each Python version, I believe. We don't have a way to set custom testing images at all currently; I think at that point you could just do the testing in a separate step after cibuildwheel runs. |
Beta Was this translation helpful? Give feedback.
-
True, but then we'll have to set up test container & emulation on our own, which defeats some of cibuildwheel's convenience... |
Beta Was this translation helpful? Give feedback.
You would need a custom testing image for each Python version, I believe. We don't have a way to set custom testing images at all currently; I think at that point you could just do the testing in a separate step after cibuildwheel runs.