From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Michael Riesch <michael.riesch@wolfvision.net>
Cc: ptxdist@pengutronix.de,
Michael Tretter <m.tretter@pengutronix.de>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [ptxdist] [PATCH 2/3] libcamera: version bump 0.0.5 -> 0.2.0
Date: Tue, 14 May 2024 18:15:19 +0200 [thread overview]
Message-ID: <ZkOOF76dfz_-PEOT@pengutronix.de> (raw)
In-Reply-To: <1fd16532-aa1c-45f2-adf1-ff2d24003efd@wolfvision.net>
On Tue, May 14, 2024 at 04:34:25PM +0200, Michael Riesch wrote:
> Hi Michael,
>
> Sorry for the long silence...
>
> On 3/5/24 19:35, Michael Tretter wrote:
> > On Tue, 05 Mar 2024 11:51:35 +0100, Michael Riesch wrote:
> >> Due to an API breakage in libcamera it may be necessary to update the
> >> consumers of the library. One example is pipewire, which needs to be
> >> updated to at least 1.0.2.
> >>
> >> Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
> >> ---
> >> rules/libcamera.make | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/rules/libcamera.make b/rules/libcamera.make
> >> index 928a95654..c9c4e2055 100644
> >> --- a/rules/libcamera.make
> >> +++ b/rules/libcamera.make
> >> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBCAMERA) += libcamera
> >> #
> >> # Paths and names
> >> #
> >> -LIBCAMERA_VERSION := 0.0.5
> >> -LIBCAMERA_MD5 := cc2f5c0c051319a7e853dc6916807ce5
> >> +LIBCAMERA_VERSION := 0.2.0
> >> +LIBCAMERA_MD5 := 08f0681221c654838e54e6b3a32f89b5
> >
> > There is a new feature flag for udev support, which should be set
> > explicitly.
>
> Hm. Why? Do you want to disable udev support explicitly?
>
> libcamera commit d314d3b9 ("libcamera: Add option to configure udev
> support") introduces the meson option but sets its default to "auto". If
> libudev is found (and it should be found, as LIBCAMERA selects
> UDEV_LIBUDEV) the new feature "Hotplug support" is enabled. As stated in
> the commit message of d314d3b9, the behavior is not changed by this commit.
>
> If one would like to disable udev support explicitly, we would need to
> introduce a ptxdist option, pass it to meson, and make the dependency on
> UDEV_LIBUDEV conditional. But personally I don't see any value in that.
'set explicitly' as in 'enable it explicitly'. This way, the build will
fail if udev is not detected correctly for some reason.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-05-14 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 10:51 [ptxdist] [PATCH 0/3] " Michael Riesch
2024-03-05 10:51 ` [ptxdist] [PATCH 1/3] libcamera: switch to canonical tarball repository Michael Riesch
2024-03-05 11:07 ` Kieran Bingham
2024-03-15 4:06 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-03-05 10:51 ` [ptxdist] [PATCH 2/3] libcamera: version bump 0.0.5 -> 0.2.0 Michael Riesch
2024-03-05 18:35 ` Michael Tretter
2024-05-14 14:34 ` Michael Riesch
2024-05-14 16:15 ` Michael Olbrich [this message]
2024-05-15 7:09 ` Michael Riesch
2024-03-05 10:51 ` [ptxdist] [PATCH 3/3] pipewire: version bump 1.0.1 -> 1.0.3 Michael Riesch
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=ZkOOF76dfz_-PEOT@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=kieran.bingham@ideasonboard.com \
--cc=m.tretter@pengutronix.de \
--cc=michael.riesch@wolfvision.net \
--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