Example of using custom CIBW repair-wheel-command
to invoke "stub_generation.py" (not included, assumed to be in the same directory as the "oiio_wheels_repair.py" file
Here's what happens:
- Just before the build initializes,
uv
is installed to the local CIBW instance. - The wheel is built as normal...
- We use
uv run --no-config
to run our custom script: A. The cross-platformrepairwheel
utility produces a "repaired" wheel consistent with what CIBW normally does if you don't specify a custom repair-wheel-command B. (Optionally, we strip out stuff we know we don't want -- this isn't doing much now, but if/when we start bundling dynamic (e.g. LGPL) libraries with the distribution, we'll want to strip out redundant "namelink copies" of shared libs to reduce wheel file size) C. Invoke the stub_generator.py script withuv run --with --no-config stub_generator.py