Filipe Laíns 🇵🇸
Filipe Laíns 🇵🇸
I am not on the computer, I will try later. But what it seemed to me is that the `_typed_visitor.py` file is missing because it failed to generate.
@atlas0fd00m do you have any documentation related to the actual RfCat (host) MCU (device) transport packets? It doesn't seem that hard to implement such a communication stack in a cheap...
The reason it used to work is because `setup.py install` used the long deprecated egg format, and setuptools could install files to arbitrary locations on the filesystem. This is not...
> This seems worse and installed even more files into the Python location. That is the correct behavior. Files cannot be installed to an arbitrary location when using wheels, so...
> And if I understand @FFY00 correctly, for your packaging, the placement of the other data files are your responsibility, so good luck with them... Yep. We can just place...
Don't you need to compile native code?
@DSheirer any ETA on this? It shouldn't be that hard since it can work as an UHD device using SoapyUHD. It would also make sense for you to support plain...
Just an heads up, all the libratbag's SVGs were moved to piper.
I think the biggest win here is really unifying the logic in one place.
> Does not it need documentation? It's missing a news entry, but other than that, no, it's an internal change. > Would not it be more useful to expose `build_prefix`...