When de6fabc got merged, the dependency that loaded winapi's sysinfoapi feature got removed. This fails builds when attempting to build font-kit downstream (i.e. if you depend on git = "https://github.com/pcwalton/font-kit.git" through Cargo.toml), but it does not fail when you run cargo build within font-kit's folder directly.
I don't know why cargo behaves that way. I assume it's a bug. Still, this fixes that behavior by making the sysinfoapi dependency explicit. For good measure, we make all the other winapi dependency features explicit to ensure this same sort of issue doesn't happen again.
When de6fabc got merged, the dependency that loaded
winapi'ssysinfoapifeature got removed. This fails builds when attempting to buildfont-kitdownstream (i.e. if you depend ongit = "https://github.com/pcwalton/font-kit.git"throughCargo.toml), but it does not fail when you runcargo buildwithinfont-kit's folder directly.I don't know why cargo behaves that way. I assume it's a bug. Still, this fixes that behavior by making the
sysinfoapidependency explicit. For good measure, we make all the otherwinapidependency features explicit to ensure this same sort of issue doesn't happen again.