From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id E3921C28D13 for ; Mon, 22 Aug 2022 08:36:03 +0000 (UTC) Received: from smtp1.axis.com (smtp1.axis.com [195.60.68.17]) by mx.groups.io with SMTP id smtpd.web08.15905.1661157356284724298 for ; Mon, 22 Aug 2022 01:35:56 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@axis.com header.s=axis-central1 header.b=fMFDijjd; spf=pass (domain: axis.com, ip: 195.60.68.17, mailfrom: peter.kjellerstedt@axis.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=axis.com; q=dns/txt; s=axis-central1; t=1661157356; x=1692693356; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=hryLh8oGmed6fDawDkAZIx0upk69Rk5q5hf4V4c7+E4=; b=fMFDijjdZNW9x4+DMtKX3HTRsvslBxSYNcXi3GT+vDcZq+VJaOa1bqqc hH+Cvlx3z4xhrjzBG1r1YUvJS5wGJZ3G0FwDnqb0lmRjMeJhkoZDw4USD r/FpUeYzj0hi9RNLn2rC0LtECdO5BtjzFB2D+Nq/BS3RMw+Ycs8qM2iY/ whtZDy/dTavBSb0Ut2WDkvMl2jhP+8+7We+hV9eTNqYbKCMS+SdBJ88dJ o+5a5Nq/Tu8xWHa31quFfS+bMDrAQ4dfmJt+7sXTH3IMMtBE5+/G8+ud9 4NTT7p1ZNwr/DjbPm0FZACB0vM+hIGvWIUUJ/8RkymL/YZ81nDCvuVZ58 w==; From: Peter Kjellerstedt To: Markus Volk CC: "openembedded-devel@lists.openembedded.org" Subject: RE: [oe] [meta-multimedia][PATCHv7] pipewire: update to v0.3.56 Thread-Topic: [oe] [meta-multimedia][PATCHv7] pipewire: update to v0.3.56 Thread-Index: AQHYtMi/yjgmzJ1YBkyhpXp9hjuVfa25SRFQ///41oCAAVZmYA== Date: Mon, 22 Aug 2022 08:35:53 +0000 Message-ID: <301d7b0dabda40eba9b037c87a8fbd4e@axis.com> References: <20220820191150.5699-1-f_l_k@t-online.de> <52f6ee030dbf4e88a86e3702a5303d57@axis.com> In-Reply-To: Accept-Language: en-US, sv-SE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.5.60] Content-Type: multipart/alternative; boundary="_000_301d7b0dabda40eba9b037c87a8fbd4eaxiscom_" MIME-Version: 1.0 List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Mon, 22 Aug 2022 08:36:03 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-devel/message/98361 --_000_301d7b0dabda40eba9b037c87a8fbd4eaxiscom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I still don't understand how you intend for a "gstreamer" distro feature to= work. You use it in the pipewire recipe to decide whether to use the "gstr= eamer" or "ffmpeg" PACKAGECONFIG by default. However, that seems very speci= fic to pipewire. We use both GStreamer and FFmpeg in our products, so using= a distro feature to distinguish between them is not something universal. //Peter From: Markus Volk Sent: den 21 augusti 2022 16:01 To: Peter Kjellerstedt Cc: openembedded-devel@lists.openembedded.org Subject: RE: [oe] [meta-multimedia][PATCHv7] pipewire: update to v0.3.56 i tried to follow your suggestions, Thanks Am So, 21. Aug 2022 um 12:49:24 +0000 schrieb Peter Kjellerstedt >: AFAIK, there are no current examples of "gstreamer" being used a distro fea= ture. What is it supposed to mean? When is it supposed to be used? Why is i= t needed? I found an example of this, but I must confess that this was in an old thir= d-party layer. What I want this DISTRO_FEATURE for is the ability to use it= to enable/disable gstreamer support in recipes. Not just here in pipewire.= The same goes for Jack. Is this already used as a DISTRO_FEATURE? If so, m= aybe we could use it to make the Jack server depend on it instead of always= building it as it currently does? --_000_301d7b0dabda40eba9b037c87a8fbd4eaxiscom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I still don’t understand how you intend for a = 220;gstreamer” distro feature to work. You use it in the pipewire rec= ipe to decide whether to use the “gstreamer” or “ffmpeg&#= 8221; PACKAGECONFIG by default. However, that seems very specific to pipewire. W= e use both GStreamer and FFmpeg in our products, so using a distro feature = to distinguish between them is not something universal.

 

//Peter

 

From: Markus Volk <f_l_k@t-online.de>
Sent: den 21 augusti 2022 16:01
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: RE: [oe] [meta-multimedia][PATCHv7] pipewire: update to v0.= 3.56

 

 

i tried to follow your suggestions,

Thanks

 

Am So, 21. Aug 2022 um 12:49:24 +0000 schrieb Pe= ter Kjellerstedt <peter.k= jellerstedt@axis.com>:

AFAIK, there are no current examples of "gstrea= mer" being used a distro feature. What is it supposed to mean? When is= it supposed to be used? Why is it needed?

 

 

I found an example of this, but I must confess that = this was in an old third-party layer. What I want this DISTRO_FEATURE for i= s the ability to use it to enable/disable gstreamer support in recipes. Not= just here in pipewire. The same goes for Jack. Is this already used as a DISTRO_FEATURE? If so, maybe we could = use it to make the Jack server depend on it instead of always building it a= s it currently does?

--_000_301d7b0dabda40eba9b037c87a8fbd4eaxiscom_--