From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] mfx_dispatch (1.35.1)
Date: Mon, 6 Feb 2023 21:22:15 +0900 [thread overview]
Message-ID: <20230206212215.895ffd3e7618f7b005ed332b@nifty.ne.jp> (raw)
In-Reply-To: <224c1d61-5299-5be6-d6f3-9f4801cd198f@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Sun, 5 Feb 2023 16:35:23 +0000
Jon Turney wrote:
> On 05/02/2023 08:39, Takashi Yano via Cygwin-apps wrote:
> > I would like to propose new package mfx_dispatch, which is
> > dev package for codecs using Intel GPUs. This is needed by
> > ffmpeg package I had proposed, and is an alternative to libmfx
> > package provided for ffmpeg-free package in fedora.
>
> Do you mean "fedora uses libmfx, but I've decided to use this instead"?
Yes.
> If so, why? Or perhaps I've misunderstood.
First, I tried to build intel-mediasdk (libmfx) used in fedora,
however, it requires libdrm, libpciaccess, etc. which could not
be built in cygwin as far as I tried.
So, I gave up building intel-mediasdk and decide to use
mfx_dispatch instead. Please note that most the code in
mfx_dispatch is borrowed from intel-mediasdk, therefore,
I think it can be treated as same as intel-mediasdk.
> > I already prepared the package at the following location.
> >
> > https://tyan0.yr32.net/cygwin/x86_64/release/mfx_dispatch/
>
> Again, libmfx should be libmfx1.
>
> You might check that for all of these packages :)
Thanks for the advice. I revised the cygport file
as attached. Is this as you expected?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
[-- Attachment #2: mfx_dispatch.cygport --]
[-- Type: text/plain, Size: 403 bytes --]
NAME="mfx_dispatch"
VERSION=1.35.1
RELEASE=1
LICENSE="BSD-3-Clause"
CATEGORY="Libs"
SUMMARY="Intel MediaSDK dispatcher (Alternative to libmfx)"
HOMEPAGE="https://github.com/lu-zero/mfx_dispatch"
SRC_URI="https://github.com/lu-zero/mfx_dispatch/archive/refs/tags/${VERSION}.tar.gz"
PKG_NAMES="libmfx1 libmfx-devel"
libmfx1_CONTENTS="usr/bin usr/share/doc/"
libmfx_devel_CONTENTS="usr/include/ usr/lib/"
prev parent reply other threads:[~2023-02-06 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 8:39 Takashi Yano
2023-02-05 16:35 ` Jon Turney
2023-02-06 12:22 ` Takashi Yano [this message]
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=20230206212215.895ffd3e7618f7b005ed332b@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-apps@cygwin.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).