* [ITP] mfx_dispatch (1.35.1) @ 2023-02-05 8:39 Takashi Yano 2023-02-05 16:35 ` Jon Turney 0 siblings, 1 reply; 3+ messages in thread From: Takashi Yano @ 2023-02-05 8:39 UTC (permalink / raw) To: cygwin-apps 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. I already prepared the package at the following location. https://tyan0.yr32.net/cygwin/x86_64/release/mfx_dispatch/ -- Takashi Yano <takashi.yano@nifty.ne.jp> ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ITP] mfx_dispatch (1.35.1) 2023-02-05 8:39 [ITP] mfx_dispatch (1.35.1) Takashi Yano @ 2023-02-05 16:35 ` Jon Turney 2023-02-06 12:22 ` Takashi Yano 0 siblings, 1 reply; 3+ messages in thread From: Jon Turney @ 2023-02-05 16:35 UTC (permalink / raw) To: Takashi Yano, cygwin-apps 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 :) ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ITP] mfx_dispatch (1.35.1) 2023-02-05 16:35 ` Jon Turney @ 2023-02-06 12:22 ` Takashi Yano 0 siblings, 0 replies; 3+ messages in thread From: Takashi Yano @ 2023-02-06 12:22 UTC (permalink / raw) To: cygwin-apps [-- 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/" ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-02-06 12:22 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2023-02-05 8:39 [ITP] mfx_dispatch (1.35.1) Takashi Yano 2023-02-05 16:35 ` Jon Turney 2023-02-06 12:22 ` Takashi Yano
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).