Unfortunately, SMB is currently not supported on MacOS and there's not a real plan on how to deal with it.
Context
SMB support is guaranteed thanks to the pavao project, which exposes native bindings to the libsmbclient for UNIX systems (while on Windows is natively supported by the OS).
Pavao actually builds on MacOS, BUT with some issues.
Issues
In order to distribute binaries for MacOS we would need to statically link libsmbclient to pavao, as we currently do for libssl and libssh2, but unfortunately, this is not achievable since samba doesn't support static builds.
Why not dynamic linking
Because we would be unable to generate the binaries of termscp, which are built statically.
What about a pure rust smb client
There is none. I tried once to implement it, but it takes a very long time (and money thanks).
Why is SMB not supported on MacOS
Unfortunately, SMB is currently not supported on MacOS and there's not a real plan on how to deal with it.
Context
SMB support is guaranteed thanks to the pavao project, which exposes native bindings to the libsmbclient for UNIX systems (while on Windows is natively supported by the OS).
Pavao actually builds on MacOS, BUT with some issues.
Issues
In order to distribute binaries for MacOS we would need to statically link libsmbclient to pavao, as we currently do for libssl and libssh2, but unfortunately, this is not achievable since samba doesn't support static builds.
Why not dynamic linking
Because we would be unable to generate the binaries of termscp, which are built statically.
What about a pure rust smb client
There is none. I tried once to implement it, but it takes a very long time (and money thanks).