You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have my own crate that has a C file with some ffmpeg helpers (e.g. I want to use a macros that is not covered by rust-ffmpeg-sys) I need a completely new separate installation and build of ffmepg to be able to link against it. even if I use "build" feature and ffmpeg-sys already cloned and built ffmpeg for my target platform
It would be amazing if in my crate's build script I'll be able to get the ffmpeg's location by simply looking into specified directory like
let ffmpeg_include_path = env::var("RUST_FFMPEG_SYS_DIRECTORY").unwrap();
cc::Build::new().file("ffmpeg_helper.c").header(Path::from(ffmpeg_include_path).join("libavcodec/avcodec.h")).compile("ffmpeg_helper");
The text was updated successfully, but these errors were encountered:
If I have my own crate that has a C file with some ffmpeg helpers (e.g. I want to use a macros that is not covered by rust-ffmpeg-sys) I need a completely new separate installation and build of ffmepg to be able to link against it. even if I use "build" feature and ffmpeg-sys already cloned and built ffmpeg for my target platform
It would be amazing if in my crate's build script I'll be able to get the ffmpeg's location by simply looking into specified directory like
The text was updated successfully, but these errors were encountered: