Pieter P

This appears to be another [distlib](https://github.com/pypa/distlib) limitation. py-build-cmake uses `distlib.util.get_platform()`. Tools like cibuildwheel set the `_PYTHON_HOST_PLATFORM` environment variable, e.g. `_PYTHON_HOST_PLATFORM='macosx-11.0-arm64'`, which does get respected. I'll have a look at implementing...

The main problem here is that py-build-cmake can only try to make a _guess_: Having `MACOSX_DEPLOYMENT_TARGET` set in the environment provides no guarantee whatsoever that the package will actually run...

Thanks for the report! > Create cmake cache not relative to source, but in package build folder. I'm afraid this kind of defeats the purpose of having a cache :)...

I have added a fix in 86dc912dbae9934f4841aabb3a0d06c5e6db49e9: If Ninja is installed in the current Python environment, its path is passed to CMake, updating the cache variable on every run.

### Question 1 I believe there are three common scenarios here: 1. You (or a user) are building packages from source locally. In this case, py-build-cmake simply uses the current...

I'll have a more detailed look at this later this week, I'll need to see how other backends such as setuptools handle platform/architecture tags. To answer your second question, I...

I'll have a more detailed look later, but I suspect that the issue is that PyPA build first creates an sdist. Then it extracts all source code from the sdist...

> on windows ends with a failure to find the file in the temporary build directory The problem here is that PyPA build changes the current working directory to its...

This is usually caused by incorrect connections. Double-check whether you've got the pins the right way around (you may have swapped ground and one of the signal pins, for example).

First of all, which messages are you _expecting_ to see? In the MIDI-OX output, data2=01means `+1`, and data2=7F means `-1`. Usually, you have four increments/decrements per physical "click" of the...