rusty_ffmpeg
rusty_ffmpeg copied to clipboard
CCExtractor
FFI bindings for FFmpeg inner libraries.
dynamic linking was trying to link to a single file this adds dynamic linking to the various .so files tested and worked
I don't have access to open a PR. I am building `rusty_ffmpeg` to target `wasm32-wasi`. Since wasm32 uses a u32 as usize, it fails to build `src/avutil/error.rs` because it looks...
I run the ”cargo build“ command to compile, but I can't find the library when I run "cargo build --target=wasm32-unknown-emscripten". They are linked to the same system library.
Currently blocked on a vcpkg issue(some dependency libs not automatically found by vcpkg). Linked issue: https://github.com/microsoft/vcpkg/issues/9571
Currently we doesn't pay much attention on when should the bindings being regenerated and when should the project being build. For example we need to take care of the `pkg_confg::Config::env_var`.
Current we got enum like this: ```rust pub const AVMediaType_AVMEDIA_TYPE_NB: AVMediaType = 5; ``` Which is not good to use. And the rust-bindgen provides us several options: However they all...
When trying to compile `rusty_ffmpeg` with `link_system_ffmpeg` on Termux, I couldn't, due to the following error: ``` Compiling rusty_ffmpeg v0.13.1+ffmpeg.6.0 error: failed to add native library /data/data/com.termux/files/usr/lib/libstdc++.a: file too small...
[Rust's opencv bindings](https://github.com/twistedfall/opencv-rust) used to just work with rusty_ffmpeg, but switching from 0.14 to 0.15 breaks linking. Adding this line to any Cargo.toml using `rusty_ffmpeg` v0.15+ causes this issue: ```toml...
This commit unifies the code for static linking under all operating systems, with a focus on fixing problems for Windows: 1. All functionality for pkg-config is now enabled for Windows...
