tl;dr: minimally failing example
Description
In a project I'm working on, we're using tokio's unstable features. Those features require opt-in through an environmnent variable. This environment variable can be set in the file .cargo/config.toml, which is what we do. Unfortunately, dist build seems to ignore this configuration. As a result, the compilation step during dist build fails.
What I've tried
- Running
RUSTFLAGS="--cfg tokio_unstable" dist build1 works fine.
- I cannot find anything applicable to this situation in the
dist book.
- I was unable to identify similar issues here on github.
Questions
- Do you consider this a bug or missing feature, or am I miss- or even abusing
dist?
- Is there a maintainable workaround? I feel uncomfortable monkey-patching the
release.yml to jam this environment variable in there every time I run dist init.
- Do you need or want any additional information?
tl;dr: minimally failing example
Description
In a project I'm working on, we're using
tokio's unstable features. Those features require opt-in through an environmnent variable. This environment variable can be set in the file.cargo/config.toml, which is what we do. Unfortunately,dist buildseems to ignore this configuration. As a result, the compilation step duringdist buildfails.What I've tried
RUSTFLAGS="--cfg tokio_unstable" dist build1 works fine.distbook.Questions
dist?release.ymlto jam this environment variable in there every time I rundist init.Footnotes
as you might expect,
RUSTFLAGS="--cfg tokio_unstable"is the environment variable configured in.cargo/config.toml↩