pyliblo3/_liblo3.c is a generated source so please do not track it with the vcs
it is better to change the scripts to project.scripts
the environment variables for cibuildwheel should be used for overriding configuration. The configuration there should be moved to pyproject.toml instead
I also have a recommendation to consider scikit-build-core as the build backend, because CMake is better suited at finding and controlling dependencies than plain include/library flags. There is an example there for cython and you would be able to fallback to building a specific version if liblo is not available on the system. This makes it a better experience for pip install when it is not able to detect a compatible wheel.
I want to comment a few things here.
pyliblo3/_liblo3.c
is a generated source so please do not track it with the vcsproject.scripts
cibuildwheel
should be used for overriding configuration. The configuration there should be moved topyproject.toml
insteadI also have a recommendation to consider
scikit-build-core
as the build backend, because CMake is better suited at finding and controlling dependencies than plain include/library flags. There is an example there forcython
and you would be able to fallback to building a specific version ifliblo
is not available on the system. This makes it a better experience forpip install
when it is not able to detect a compatible wheel.