> Aha! It can - if one uses propagated-inputs in the package recipes. I think > the importer should propagate inputs if the current package is > Rust-source-only. Otherwise packages further down the dependency graph > (further to the clients) won't compile later.
One of the ideas behind the [replace] stuff in the Cargo.toml file was to retain the required dependencies. > However, some of the Rust crates have a "windows" target which fails. > For these I'd like to pass "--cfg=unix" and I'd like to put it into the > package recipe and not hardcode it into the build system. Nice, didn't know about this flag. That explains why it refused to build without the windows dependencies.
