Closed
Description
openedon Jun 5, 2017
(Moved and re-phrased from #97)
Currently cargo can pass env vars from up-stream dependencies to down-stream, with user-defined metadata.
But what's still lacking is the reversed control, where up-stream library expects a env var to be set to build successfully, and down-stream must fill the env var for it.
This scenario is common in FFI libraries wrapping existing C lib, for example meh/rust-ffmpeg-sys expects the env var FFMPEG_DIR to be set to the path of pre-built C FFMpeg libs & binaries.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment