-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ffmpeg-next won't build on windows. Non exhaustive patterns. #126
Comments
It seems that the following enums were missing some match arms. I've cloned this repo and had my editor automatically generate the missing match arms: This compiler error doesn't seem to affect linux builds. impl<From<AVPixelFormat> for Pixel{
// Current match arms elided
AV_PIX_FMT_VUYA => todo!(),
AV_PIX_FMT_RGBAF16BE => todo!(),
AV_PIX_FMT_RGBAF16LE => todo!(),
AV_PIX_FMT_VUYX => todo!(),
AV_PIX_FMT_P012LE => todo!(),
AV_PIX_FMT_P012BE => todo!(),
AV_PIX_FMT_Y212BE => todo!(),
AV_PIX_FMT_Y212LE => todo!(),
AV_PIX_FMT_XV30BE => todo!(),
AV_PIX_FMT_XV30LE => todo!(),
AV_PIX_FMT_XV36BE => todo!(),
AV_PIX_FMT_XV36LE => todo!(),
AV_PIX_FMT_RGBF32BE => todo!(),
AV_PIX_FMT_RGBF32LE => todo!(),
AV_PIX_FMT_RGBAF32BE => todo!(),
AV_PIX_FMT_RGBAF32LE => todo!(),
} impl From<AVCodecID> for Id{
// Current match arms elided
AV_CODEC_ID_RADIANCE_HDR => todo!(),
AV_CODEC_ID_WBMP => todo!(),
AV_CODEC_ID_MEDIA100 => todo!(),
AV_CODEC_ID_VQC => todo!(),
AV_CODEC_ID_BONK => todo!(),
AV_CODEC_ID_MISC4 => todo!(),
AV_CODEC_ID_APAC => todo!(),
AV_CODEC_ID_FTR => todo!(),
} Could this be a matter of creating enum variants for pub enum Pixel{
// Current variants elided
#[cfg(target_os = "windows")]
YUVA
} and then the following match arms in the impl From<AVPixelFormat> for Pixel{
// Current match arms elided
#[cfg(target_os = "windows")]
AV_PIX_FMT_VUYA => Pixel::YUVA,
} Also if it's relevant, my installed version of ffmpeg is |
happens for me too, should I just build it on linux from now on? |
I can build it outside of the other crate on windows, but that crate won't compile.... |
my issue seems to be with
|
It seems to not like to build in its dev env, not knowing the things that are missing, but works when the branches are added and just used in another crate. Is this a quirk of how rust bindings work? |
(I probably missed something when adding them (may be feature flag stuff.)) |
It's related to what version of ffmpeg library you use. |
OS: Windows 10
Ffmpeg version: ffmpeg-master-latest-win64-gpl-shared. 12/24/2022
I followed the installation guide from the wiki for building on windows. I have downloaded the latest ffmpeg windows build and set the
FFMPEG_DIR
variable accordingly.I get the following error when building my project that depends on ffmpeg-next in windows.
This project compiles just fine in linux
The text was updated successfully, but these errors were encountered: