From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] mfx_dispatch (1.35.1)
Date: Sun, 5 Feb 2023 16:35:23 +0000 [thread overview]
Message-ID: <224c1d61-5299-5be6-d6f3-9f4801cd198f@dronecode.org.uk> (raw)
In-Reply-To: <20230205173914.b106f517fb904a36e28da758@nifty.ne.jp>
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"?
If so, why? Or perhaps I've misunderstood.
> 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 :)
next prev parent reply other threads:[~2023-02-05 16:35 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 [this message]
2023-02-06 12:22 ` Takashi Yano
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=224c1d61-5299-5be6-d6f3-9f4801cd198f@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).