Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] qsv: add requirement for the mininal version of libmfx
Date: Thu, 26 May 2022 00:42:41 +0000
Message-ID: <5ec39988a81b90bc55bef74df3a40eedaa0200a1.camel@intel.com> (raw)
In-Reply-To: <2fb3cc47-05a5-4268-c5e7-922ad12592bc@gmail.com>

On Wed, 2022-05-25 at 12:22 -0400, Leo Izen wrote:
> 
> On 5/25/22 12:05, Timo Rothenpieler wrote:
> > 
> > 
> > On 22/05/2022 14:19, Haihao Xiang wrote:
> > > libmfx 1.28 was released 3 years ago, it is easy to get a greater
> > > version than 1.28. We may remove lots of compile-time checks if adding
> > > the requirement for the minimal version in the configure script.
> > > ---
> > >   configure                  |   7 +-
> > >   libavcodec/qsv.c           |  24 --
> > >   libavcodec/qsvenc.c        | 471 +++++++++++++------------------------
> > >   libavcodec/qsvenc.h        |  51 +---
> > >   libavcodec/qsvenc_h264.c   |   6 -
> > >   libavcodec/qsvenc_hevc.c   |  10 -
> > >   libavfilter/vf_scale_qsv.c |  13 +-
> > >   libavfilter/vf_vpp_qsv.c   | 143 ++++++-----
> > >   libavutil/hwcontext_qsv.c  |   2 -
> > >   9 files changed, 249 insertions(+), 478 deletions(-)
> > > 
> > > diff --git a/configure b/configure
> > > index f115b21064..2337f0a8f2 100755
> > > --- a/configure
> > > +++ b/configure
> > > @@ -6566,8 +6566,11 @@ enabled liblensfun        && require_pkg_config 
> > > liblensfun lensfun lensfun.h lf_
> > >   # Media SDK or Intel Media Server Studio, these don't come with
> > >   # pkg-config support.  Instead, users should make sure that the build
> > >   # can find the libraries and headers through other means.
> > > -enabled libmfx            && { check_pkg_config libmfx libmfx 
> > > "mfx/mfxvideo.h" MFXInit ||
> > > -                               { require libmfx "mfx/mfxvideo.h" 
> > > MFXInit "-llibmfx $advapi32_extralibs" && warn "using libmfx without 
> > > pkg-config"; } }
> > > +enabled libmfx            && { check_pkg_config libmfx "mfx >= 1.28" 
> > > "mfx/mfxvideo.h" MFXInit ||
> > > +                               { require libmfx "mfx/mfxvideo.h 
> > > mfx/mfxdefs.h" MFXInit "-llibmfx $advapi32_extralibs" &&
> > 
> > This broke build with mfx_dispatch. Before this, it checked for 
> > libmfx.pc. Now it checks for mfx.pc, which is not installed by it.
> > 
> > Which of those is correct? It should definitely not drop support for 
> > libmfx.pc, which was checked before this.
> 
> It also attempts to link to -llibmfx, which means liblibmfx.so. I'm 
> guessing it's supposed to link to -lmfx instead.

It is -llibmfx in the original code. Please see commit
164e2773261451ef33c4616296ec5bebecff42af for why it is -llibmfx instead of -lmfx
here.

Thanks
Haihao

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2022-05-26  0:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 12:19 Haihao Xiang
2022-05-22 14:04 ` Jean-Baptiste Kempf
2022-05-22 18:09 ` Soft Works
2022-05-24  8:46   ` Xiang, Haihao
2022-05-25 16:05 ` Timo Rothenpieler
2022-05-25 16:22   ` Leo Izen
2022-05-26  0:42     ` Xiang, Haihao [this message]
2022-05-26  0:39   ` Xiang, Haihao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ec39988a81b90bc55bef74df3a40eedaa0200a1.camel@intel.com \
    --to=haihao.xiang-at-intel.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git