Rob Moran
Rob Moran
We recently ported [node-usb](https://github.com/node-usb/node-usb) to `prebuildify` using `prebuildify-cross`, it may serve as inspiration. Coupled with a port to `node-addon-api` it should fix most platform issues and future proof the library....
Just hit this issue, any idea where the problem may be?
On Windows it looks like it's just incrementing an internal counter which makes it unique (to this library) but certainly isn't correct: https://github.com/MadLittleMods/node-usb-detection/blob/d87c4669c5fcfd4c4d963892f17c1ba74456beb8/src/detection_win.cpp#L424
In [node-usb](https://github.com/node-usb/node-usb) we switched to `prebuildify` and `prebuildify-cross` on GH Actions to gain the broader architecture support.
The packs shipped with Mbed Studio are stripped down and only contain the debug data. You can specify a pack to use with PyOCD using the `--pack` switch. Look at...
> Unfortunately I cannot find any logs in mbed studio Help > Report an Issue > Access Log
Relates to #40
Unfortunately I'm not a Java developer with a setup to modify and build any changes for this nor the time to invest in setting this up and learning the systems....
Also see benefits as outlined by @vweevers in https://github.com/atom/node-keytar/issues/255#issuecomment-598727183
+1 This switch would be very useful for when the target architecture is unknown at build time, e.g. building a VSCode extension.