Build/Test/Repair multiple projects

[LecrisUT]

I am currently working on a project that has multiple sub-projects that have to be built with version sync between each other and would require the repair step to pull in the recently built (and repaired) wheels from the previous step. But getting that to works is really difficult, especially with the linux runners running in containers.

Instead what would help is for package_dir to accept a comma-separated list, and have all the steps run in groups, BEFORE_ALL -> BEFORE_BUILD -> BUILD_ALL_WHEELS -> REPAIR_ALL_WHEELS etc. It would also help to have the format variables more widely available in all the steps.

[joerick]

I think due to the complexity involved, that's unlikely to be a feature that we offer. Each package can contain its own pyproject.toml, so we'd have to somehow combine the configs for each package with some global config for how the flow works. It would be difficult to justify the complexity IMO.

Have you tried using PIP_FIND_LINKS to try to get a subsequent build to use previously built wheels?

[LecrisUT]

Each package can contain its own pyproject.toml, so we'd have to somehow combine the configs for each package with some global config for how the flow works. It would be difficult to justify the complexity IMO.

What if we restrict the scope that only the top pyproject.toml is read for the configuration without merging the configs. It is likely that if they have such a complex inter-dependency, they would also have a meta-package to organize common tooling.

I am thinking of having a tool.cibuildwheel.packages which accepts a list of packages to build with the current configuration.

Have you tried using PIP_FIND_LINKS to try to get a subsequent build to use previously built wheels?

Yes, but it was not successful on the ubuntu runners that were running through containers and/or the wheel tags were not matching.