Rust build scripts for crates that rely on external (ie. C ABI) libraries are completely naive, and rely almost exclusively on either the automake tools, cmake or (most often) simply that the right version of the library dependency is already magically present on the system due to apt-get or some other user configuration.<p>Compiling <i>pure rust</i> relies on the single compiler toolchain which is assumed to be present by cargo, and universal on all platforms. That&#x27;s pretty solid.<p>...but rust = no autoconf is somewhat misleading; rust that uses c libraries has to solve all the same problems that anything else using c libraries has to; but unlike python or node, there is no help (ie. gyp or distutils) for you if you need to do this.<p>Perhaps eventually something clever will come along to fill the gap, but it&#x27;s something of a pain point at the moment, especially on windows.