Josh Stone

When it comes to supply-chain, you also don't know who the current owners may invite tomorrow. I think a pending invitation is not so different, just a step closer, as...

> Autocfg emitting the rerun-if-env-changed sounds reasonable but is not a straightforward best choice. It doesn't do that implicitly, and I'm convinced by your argument that it would be problematic....

Hmm, I don't have a way to do this though: https://github.com/dtolnay/anyhow/blob/028cbeedf5e94970c088eb14e325744086a7b768/build.rs#L117-L119

Well, the problem starts from using `link_deps()`, wherever the actual bug may lie. :smile: Note that your `"{:?}"` (`Debug`) added the quotation marks though. So `link_deps()` flattens to `target_rustcflags`, and...

Right. We were only adding the cargo target dirs before, not all of `PATH` -- I'll just go back to that, not a big deal. But since your README now...

For `indexmap` in particular, it also has a cargo feature `"std"` that bypasses the `autocfg` check. If you add that dependency to your project with the feature enabled, cargo will...

Is there a wrapper or something that sets the sysroot or library search path? I'm not sure what's missing here...

Did you truncate that `tree` at `rustlib`, or is that empty? The `$sysroot/lib` is used at runtime, but for builds `rustc` will look in `$sysroot/lib/rustlib/$target/lib` by default. As for environment,...

> `rustc` will look in `$sysroot/lib/rustlib/$target/lib` by default. I just remembered there's a concise command to find this, `rustc --print target-libdir`.

I'm open to folks experimenting with this, but I think it will be nontrivial to plumb that condition through everywhere.