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
CONFIGURE FFMPEG #729
Comments
|
We implemented a libXCam video filter for FFMPEG, but we have not submitted the video filter to FFMpeg official repo…
From: logindiamant <notifications@github.com>
Sent: Thursday, June 4, 2020 9:00 PM
To: intel/libxcam <libxcam@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [intel/libxcam] CONFIGURE FFMPEG (#729)
Dear colleagues, please tell us, how to configure libxcam in ffmpeg?
I try to build ffmpeg by sources, step by step
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
...
When I try to compile ffmpeg with
cd ~/ffmpeg_sources &&
wget -O ffmpeg-snapshot.tar.bz2 https://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2 &&
tar xjvf ffmpeg-snapshot.tar.bz2 &&
cd ffmpeg &&
PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure
--prefix="$HOME/ffmpeg_build"
--pkg-config-flags="--static"
--extra-cflags="-I$HOME/ffmpeg_build/include"
--extra-ldflags="-L$HOME/ffmpeg_build/lib"
--extra-libs="-lpthread -lm"
--bindir="$HOME/bin"
--enable-gpl
--enable-gnutls
--enable-libaom
--enable-libass
--enable-libfdk-aac
--enable-libfreetype
--enable-libmp3lame
--enable-libopus
--enable-libvorbis
--enable-libvpx
--enable-libx264
--enable-libx265
--enable-libxcam
--enable-nonfree &&
PATH="$HOME/bin:$PATH" make &&
make install &&
hash -r
...
I see error
Unknown option "--enable-libxcam".
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#729>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACXDSP4OYDIVT2XTO5CV4JLRU6LELANCNFSM4NSTHGMQ>.
|
|
@zongwave, please, send us unofficial FFMPEG build with libXCam… |
|
Hi, we have to go through Intel Open Source process before publish this FFMPEG video filter. I’ll inform you then.
Thanks,
Zong Wei
From: logindiamant <notifications@github.com>
Sent: Thursday, June 4, 2020 10:20 PM
To: intel/libxcam <libxcam@noreply.github.com>
Cc: Zong, Wei <wei.zong@intel.com>; Mention <mention@noreply.github.com>
Subject: Re: [intel/libxcam] CONFIGURE FFMPEG (#729)
@zongwave<https://github.com/zongwave>, please, give us unofficial FFMPEG build with libXCam…
email: gleb.derzkij@gmail.com<mailto:gleb.derzkij@gmail.com>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#729 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACXDSP6BCOG6KHSMEMDZQL3RU6UPFANCNFSM4NSTHGMQ>.
|
|
I’m also wondering how to configure libxcam for ffmpeg on Ubuntu. Has this went through the Intel open source process yet? |
|
Please refer to this patch we submitted to FFMpeg patchwork |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear colleagues, please tell us, how to configure libxcam in ffmpeg?
I try to build ffmpeg by sources, step by step
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
...
When I try to compile ffmpeg with
cd ~/ffmpeg_sources &&
wget -O ffmpeg-snapshot.tar.bz2 https://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2 &&
tar xjvf ffmpeg-snapshot.tar.bz2 &&
cd ffmpeg &&
PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure
--prefix="$HOME/ffmpeg_build"
--pkg-config-flags="--static"
--extra-cflags="-I$HOME/ffmpeg_build/include"
--extra-ldflags="-L$HOME/ffmpeg_build/lib"
--extra-libs="-lpthread -lm"
--bindir="$HOME/bin"
--enable-gpl
--enable-gnutls
--enable-libaom
--enable-libass
--enable-libfdk-aac
--enable-libfreetype
--enable-libmp3lame
--enable-libopus
--enable-libvorbis
--enable-libvpx
--enable-libx264
--enable-libx265
--enable-libxcam
--enable-nonfree &&
PATH="$HOME/bin:$PATH" make &&
make install &&
hash -r
...
I see error
Unknown option "--enable-libxcam".
The text was updated successfully, but these errors were encountered: