musllinux options

[MrBitBucket]

Is it possible to specify explicit build options for the musl builds? I have tried to build reportlab musllinux, but it seems that we need to install a few packages there to make things work properly. In my alpine vm I need to do something like

. I tried the docker for musil eg

to get a wheel built, installed and tested.

I have this

CIBW_BEFORE_BUILD_LINUX: sh -c 'yum install cairo-devel fribidi -y || true'

but I am pretty unclear what the build environment is for musl using

docker run -it 'quay.io/pypa/musllinux_1_1_x86_64:2021-09-19-a5ef179' /bin/ash

and it doesn't have yum, but my apk commands work fine. So I guess I'm asking if I can use options with names like

CIBW_BEFORE_BUILD_MANYLINUX or CIBW_BEFORE_BUILD_MUSLLINUX?

[henryiii]

Please see overrides. They were added at the same time as musllinux for this purpose. (Also they are helpful in other cases, like if you mix manylinux_2_24 with any older manylinux, since that's apt and yum, respectively.)

[henryiii]

Example from the docs is for musllinux specifically. Something like this:

[tool.cibuildwheel.linux]
before-all = "yum install cairo-devel fribidi -y"

[[tool.cibuildwheel.overrides]]
select = "*-musllinux*"
before-all = "apk add cairo-devel fribidi -y"

Keep in mind, Alpine has broken compatibility with the musllinux standard in version 3.14 by applying a patch not added to CPython (#934). Until they fix that, it's probably a low priority to support them.

[MrBitBucket]

Thanks; so these overrides can only be used in the config. I guess it's time to get into another option language or split the build action.

[henryiii]

I would highly recommend using TOML to control the static build options, and only use env vars to control matrix specific settings (mostly CIBW_BUILD). This will give the added benefit that it becomes much easier to run cibuildwheel locally, and you have fewer ties to the specific CI provider.

If you use the default pyproject.toml, you should also specify the build backend and requirements. See https://scikit-hep.org/developer.