David Grayson

It's probably best to call `libusbp_device_get_os_id` and use that to retrieve the friendly name from SetupAPI. Does that work well enough? On Wed, Dec 7, 2022, 7:47 AM jporcher ***@***.***>...

The "OS ID" on Windows is a Device Instance ID, not a hardware ID. (It couldn't be a hardware ID because those are not unique when you plug two identical...

A libusbp::device represents an actual physical device plugged into a USB port, not an interface/service provided by the device, so it is correct that the only libusbp::device there is "USB...

I don't know much about flakes but we did have a pull request about it on the mirror repository: https://github.com/pololu/nixcrpkgs/pull/7

I don't know what code you are using to find libexslt: your bug reports should include all the details necessary to reproduce the bug without us having to think too...

I'm glad you are enjoying the project! I do recommend using Qt 6 (`env.qt6`) if you can: it took much less effort for me to port it, and I didn't...

Don't forget my previous comment: > Also, note that anything you get from `nixpkgs` is going to be built for your native system by the nixpkgs compiler toolchain, so it's...

Maybe qmake is setting PKG_CONFIG_PATH somewhere and overriding what you're trying to do. Also, nixpkgs itself probably has setup scripts written in Bash which override it. You should at least...

You can add the package in your fork of nixcrpkgs the same way other packages are added. Or if you want the code to live outside of nixcrpkgs, when you...

Oh, if you actually did succeed in cross-compiling a package with Nixpkgs and you want to use it with nixcrpkgs you could try putting it in the `cross_inputs` argument to...