From: Peter Korsgaard <peter@korsgaard.com>
To: Quentin Schulz <foss+buildroot@0leil.net>
Cc: buildroot@buildroot.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Marcus Folkesson <marcus.folkesson@gmail.com>,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [Buildroot] [PATCH] package/libcamera: force-disable qcam for now
Date: Tue, 11 Mar 2025 19:15:22 +0100 [thread overview]
Message-ID: <87ldtbfn7p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250311-libcamera-qt6-v1-1-4897aadc6fe3@cherry.de> (Quentin Schulz's message of "Tue, 11 Mar 2025 12:48:53 +0100")
>>>>> "Quentin" == Quentin Schulz <foss+buildroot@0leil.net> writes:
> From: Quentin Schulz <quentin.schulz@cherry.de>
> qcam is based on Qt6 since commit 71aa3ceec30b ("apps: qcam: Port to Qt
> 6") which is part of the v0.3.1 release.
> qcam being enabled when BR2_PACKAGE_QT5BASE_WIDGETS symbol is defined
> breaks the build as it's missing the qt6 dependencies.
> The migration to Qt 6 for the Buildroot package isn't straightforward
> though as we're hitting a meson bug[1].
> For now, let's just always disable qcam until we can get everything
> fixed and migrated properly.
> [1] https://github.com/mesonbuild/meson/issues/13018
> Fixes: 72757d111a5d ("package/libcamera: bump to version 0.3.2")
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Committed after adding an autobuilder reference, thanks.
> ---
> This is suboptimal solution to unbreaking Buildroot builds of libcamera
> when Qt5 Widgets are enabled but that should do for Buildroot 2025.02
> release.
> We should ideally work on adding proper support for qcam in a later
> commit, once the issue reported in
> https://github.com/mesonbuild/meson/issues/13018 is either fixed or
> worked around in Buildroot.
> FWIW, I went as far as:
> ```
> ifeq ($(BR2_PACKAGE_QT6BASE_WIDGETS)$(BR2_PACKAGE_QT6_OPENGL),yy)
> LIBCAMERA_CONF_OPTS += -Dqcam=enabled
> LIBCAMERA_DEPENDENCIES += qt6base
> else
> LIBCAMERA_CONF_OPTS += -Dqcam=disabled
> endif
> ```
> as Qt6 OpenGL module seems required now. Additionally, the Qt6 tools
> dependency is doing nothing so it can be removed. It actually never did
> anything but turn a check from meson from red to green in the configure
> step, the binaries with and without Qt tools (qt5 or qt6) were always
> identical to the bit.
Thanks for investigating!
> There are also a number of other changes we should be making to the
> recipe as libcamera is extended without knobs if libdrm, libsdl2,
> libjpeg, libdw and/or libunwind are provided. So we should add those to
> LIBCAMERA_DEPENDENCIES if they are part of the build, to make builds
> reproducible.
Will you send patches for that as well?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-03-11 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 11:48 [Buildroot] [PATCH] package/libcamera: force-disable qcam for now Quentin Schulz
2025-03-11 18:15 ` Peter Korsgaard [this message]
2025-03-12 9:51 ` Quentin Schulz via buildroot
2025-03-18 11:22 ` Quentin Schulz via buildroot
2025-03-18 14:48 ` Quentin Schulz via buildroot
2025-03-16 20:25 ` Peter Korsgaard
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=87ldtbfn7p.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=foss+buildroot@0leil.net \
--cc=kieran.bingham@ideasonboard.com \
--cc=marcus.folkesson@gmail.com \
--cc=quentin.schulz@cherry.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