mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] v4l-utils: fix libv4l2 dependencies
Date: Fri, 14 Feb 2025 10:02:15 +0100	[thread overview]
Message-ID: <20250214090215.2798024-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250203131708.2135868-1-m.tretter@pengutronix.de>

Thanks, applied as 2d39968ecba616101db7c251cec918273acc0126.

Michael

[sent from post-receive hook]

On Fri, 14 Feb 2025 10:02:15 +0100, Michael Tretter <m.tretter@pengutronix.de> wrote:
> If v4l2-ctl and v4l2-compliance are built with libv4l2, they depend on
> libv4lconvert, too.
> 
> On the other hand v4l2-dbg, doesn't depend on libv4l2 at all.
> 
> Fix the dependencies.
> 
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> Message-Id: <20250203131708.2135868-1-m.tretter@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/v4l-utils.in b/rules/v4l-utils.in
> index bb444213b7b0..6c5d892906d5 100644
> --- a/rules/v4l-utils.in
> +++ b/rules/v4l-utils.in
> @@ -81,16 +81,17 @@ config V4L_UTILS_RDSCTL
>  config V4L_UTILS_V4L2COMPLIANCE
>  	bool
>  	select V4L_UTILS_LIBV4L2
> +	select V4L_UTILS_LIBV4LCONVERT
>  	prompt "install v4l2-compliance"
>  
>  config V4L_UTILS_V4L2DBG
>  	bool
> -	select V4L_UTILS_LIBV4L2
>  	prompt "install v4l2-dbg"
>  
>  config V4L_UTILS_V4L2CTL
>  	bool
>  	select V4L_UTILS_LIBV4L2
> +	select V4L_UTILS_LIBV4LCONVERT
>  	prompt "install v4l2-ctl"
>  
>  config V4L_UTILS_V4L2SYSFSPATH



      reply	other threads:[~2025-02-14  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 13:17 [ptxdist] [PATCH] " Michael Tretter
2025-02-14  9:02 ` Michael Olbrich [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=20250214090215.2798024-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=m.tretter@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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