Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Taruntej Kanakamalla <tarun@centricular.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "sebastian@centricular.com" <sebastian@centricular.com>,
	"nirbheek@centricular.com" <nirbheek@centricular.com>
Subject: Re: [OE-core] [PATCH] gstreamer1.0-plugins-rs: add new package
Date: Sun, 24 May 2026 07:32:24 +0530	[thread overview]
Message-ID: <01d286fdf64dedc49f10f7119d42e292adf224ea.camel@centricular.com> (raw)
In-Reply-To: <DB5PR02MB10213BD65229D53D15895FD37EF062@DB5PR02MB10213.eurprd02.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Hi Peter,

On Wed, 2026-05-13 at 07:56 +0000, Peter Kjellerstedt wrote:
> Are the plugins built as single binaries, or is it one binary containing all plugins?

The plugins are built as single binaries.

>  If it is separate binaries, then\r  being able to install plugins individually is very important when you have multiple products being built from the same code base, but with different needs for which plugins they need. Flash size is unfortunately a limited resource, especially with today’s\r  memory prices. Otherwise we will have to make the recipe machine specific, which I’d rather avoid.  

Agreed. I have made changes in the latest patch (V3) and each plugin is declared as a PACKAGE now. So I think these packages can grouped together into multiple PACKAGEGROUPS for different images. Please let me know if I am missing something.

Thanks,

Tarun\r 

[-- Attachment #2: Type: text/html, Size: 995 bytes --]

  reply	other threads:[~2026-05-24  8:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 13:34 [PATCH] gstreamer1.0-plugins-rs: add new package Taruntej Kanakamalla
2026-05-12 10:30 ` [OE-core] " Mathieu Dubois-Briand
2026-05-13  7:14   ` Taruntej Kanakamalla
2026-05-12 19:28 ` Peter Kjellerstedt
2026-05-13  7:25   ` Taruntej Kanakamalla
2026-05-13  7:56     ` Peter Kjellerstedt
2026-05-24  2:02       ` Taruntej Kanakamalla [this message]
2026-05-13  7:11 ` [PATCH v2] " Taruntej Kanakamalla
2026-05-13 10:19   ` [OE-core] " Alexander Kanavin
2026-05-13 11:23     ` Nirbheek Chauhan
2026-05-13 11:45       ` Alexander Kanavin
2026-05-13 12:02         ` Nirbheek Chauhan
2026-05-13 12:15           ` Alexander Kanavin
2026-05-13 13:10             ` Nirbheek Chauhan
2026-05-24  1:51         ` Taruntej Kanakamalla
2026-05-24  1:23   ` [PATCH v3] " Taruntej Kanakamalla
2026-05-24 10:12     ` [OE-core] " Alexander Kanavin
2026-05-25 17:06       ` Peter Kjellerstedt
2026-07-07  8:21         ` Taruntej Kanakamalla
2026-05-29 13:57       ` Taruntej Kanakamalla
2026-07-07  8:17     ` [PATCH v4] " Taruntej Kanakamalla
2026-07-08  6:20       ` [OE-core] " Richard Purdie
     [not found]       ` <18C03C30DCBC1651.550146@lists.openembedded.org>
2026-07-08  6:24         ` Richard Purdie
2026-07-14 10:55       ` [PATCH v5 1/2] cargo_c.bbclass: pass --libdir to cargo cinstall Taruntej Kanakamalla
2026-07-14 10:55         ` [PATCH v5 2/2] gstreamer1.0-plugins-rs: add new package Taruntej Kanakamalla
2026-07-15 11:37           ` [OE-core] " Mathieu Dubois-Briand

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=01d286fdf64dedc49f10f7119d42e292adf224ea.camel@centricular.com \
    --to=tarun@centricular.com \
    --cc=nirbheek@centricular.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=sebastian@centricular.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