2 ms·
Nothing specific to rust. So do most other compiler and/or build-systems, but then we'd not have such a clickbaity title... Solution to that and more problems:
by tlamponi 6y ago
Nothing specific to rust. So do most other compiler and/or build-systems, but then we'd not have such a clickbaity title...
Solution to that and more problems: build in a clean chroot or container with the minimum of dependencies installed.
That's better anyway, not only due to leakage of build directory paths, but due to some projects just auto-picking up dependencies and enable the respective features if they find the libraries and the header files in the build system. For example, QEMU does this, but is not the single one to do so, but probably one where one notices this so much as it has just so many damn features!
Naturally one can disable all unwanted features explicitly in the build system, but as every release three new one are added, and it's just better to have a clean environment anyway (avoids "oops, I installed a newer GCC version to test something, and broke ABI by accident"), that is a valid solution too in my book.