Open cboulay opened 3 years ago
It's not really something we do, as piwheels is a very automated process. Alternatively, you can build the wheels and send to us for direct upload.
Is there an API or a web interface so we can upload the wheel without bothering you? I don't have a wheel at the moment. Next time I fire up my pi I'll build it and attach it here.
No API, we only do this for a couple of packages.
Package name: pylsl Link to PyPI page: https://pypi.org/project/pylsl Link to piwheels page: https://www.piwheels.org/project/pylsl Version: all Python version: all I am the maintainer: Yes More information:
Our current approach for deploying pylsl is to download our built platform-specific
liblsl
shared libraries and package them inside the wheel before uploading the wheel to pypi. This is handled by our AppVeyor script.We do not currently have an apt-installable liblsl package. This library traditionally was used mostly to stream and sync data from hardware devices for which the only available drivers were in Windows, so there wasn't much need. But things are changing so maybe we should do this. But for now let's assume it isn't available.
liblsl can be built from source relatively easily with only cmake as a dependency. We have a build script that works on raspberry pi here. We should have a raspberry pi compatible .so file on our latest release fairly soon: https://github.com/sccn/liblsl/releases/tag/v1.14.0b4
Given the above, how do we get piwheels to (a) download this .so and drop it into the correct folder before building the wheel, or (b) build liblsl itself? If (b) is the better answer then can you please point me to a project that similarly downloads a 3rd party library source, builds it, then includes the .so in the wheel? Can this all be achieved by some setup.py magic?
Cheers, Chad