Due to some third party library, I have a situation where:
LD_PRELOAD=foo.bar cargo run --example yay
cargo run --example yay
The nice thing to do would be to figure out wtf is going on in the third party library, write a patch, and submit a pull request.
I’m lazy. Is thee a way to hard code the LD_PREOAD into Cargo.toml ? Right now, when using IntelliJ, my examples/unit-tests are running without the LD_PRELOAD (and crashes), which forces mt to manually open up the “runtime env” of each example/env, tell IntelliJ to add the LD_PRELOAD, … . I would prefer a way where I can just hard code this in Cargo.toml (or some other file) so that “cargo run” anywhere inside this crate always adds the LD_PRELOAD.