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
The rusty_ffmpeg crate uses ffmpeg's build results(some header files and some package-config files) to generate bindings in the build script.
This crate can be built successfully in a local environment with PKG_CONFIG_PATH environment variable set to path where the *.pc files is located in.
However, it's super weird that this crate built successfully on the doc.rs where no FFmpeg is compiled and no environment variable is set. If you check the sources you will find that no FFmpeg sources is provided.
I suspect that the docker environment contains FFmpeg? Or the docs.rs uses the bindgen result locally?(I think the second is less possible) Or any other reason? Anyway, this really confuses me....
The text was updated successfully, but these errors were encountered:
Crate name:
rusty_ffmpeg
Build success link:
https://docs.rs/crate/rusty_ffmpeg/0.1.1/builds/264209
Additional details:
Hm, creating a issue about a successful build sounds strange. But you will find it confusing.
The rusty_ffmpeg crate uses ffmpeg's build results(some header files and some package-config files) to generate bindings in the build script.
This crate can be built successfully in a local environment with PKG_CONFIG_PATH environment variable set to path where the *.pc files is located in.
However, it's super weird that this crate built successfully on the doc.rs where no FFmpeg is compiled and no environment variable is set. If you check the sources you will find that no FFmpeg sources is provided.
I suspect that the docker environment contains FFmpeg? Or the docs.rs uses the bindgen result locally?(I think the second is less possible) Or any other reason? Anyway, this really confuses me....
The text was updated successfully, but these errors were encountered: