You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having trouble using this crate (or rather, ethers-rs ledger support which depends on summa-tx/coins, which depends on this)
I'm compiling a cross-platform binary (windows, linux, macos), and the macos binary fails to run because it is dynamically linked to libusb.
Now, I don't know much about USB itself. from studying this crate's code, my interpretation is that macos only uses libhidapi.a, and libusb is only used for linux & illumos.
so I'd guess the problem is that macos is unnecessarily linking to libusb.
It could also be that it does indeed use it, in which case I'd like to find a way to statically link it, which probably involves a chance in this crate
Would appreciate any pointers. happy to do the heavy lifting myself
dep tree on a macos build:
runtime crash:
The text was updated successfully, but these errors were encountered:
the artifact from that build is a binary that is dynamically linked against libusb.
running the same build on a local macos VM produces a different result (no linking to libusb)
I'm having trouble using this crate (or rather, ethers-rs ledger support which depends on summa-tx/coins, which depends on this)
I'm compiling a cross-platform binary (windows, linux, macos), and the macos binary fails to run because it is dynamically linked to
libusb
.Now, I don't know much about USB itself. from studying this crate's code, my interpretation is that macos only uses
libhidapi.a
, and libusb is only used for linux & illumos.so I'd guess the problem is that macos is unnecessarily linking to libusb.
It could also be that it does indeed use it, in which case I'd like to find a way to statically link it, which probably involves a chance in this crate
Would appreciate any pointers. happy to do the heavy lifting myself
dep tree on a macos build:
runtime crash:
The text was updated successfully, but these errors were encountered: