Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Philipp Ludwig" <philipp.ludwig@passerro.de>, <buildroot@buildroot.org>
Subject: Re: [Buildroot] Build failure on qt5webkit
Date: Wed, 16 Jul 2025 18:21:05 +0200	[thread overview]
Message-ID: <DBDM80RGBKL3.28PXMVWQU0RW8@bootlin.com> (raw)
In-Reply-To: <13e60f08-7ff6-43d6-bfbe-54f3aa68b96f@passerro.de>

Hi  Philipp,

On Wed Jul 16, 2025 at 8:19 AM CEST, Philipp Ludwig wrote:
> On 7/15/25 14:42, Alexis Lothoré via buildroot wrote:
>> I am facing a build issue with qt5webkit package on buildroot 2025.02.x.
>> The build outputs the following error:
>> 
>> /home/alexis/src/buildroot/output/host/opt/ext-toolchain/arm-buildroot-linux-gnueabihf/include/c++/14.2.0/type_traits:1237:52: error: non-constant condition for static assertion
>
>> I am not very fluent in C++, so I struggle to fix it. Based on the build
>> logs, I guess it relates to some missing some header include
>> (ContentSecurityPolicyHash.h, I believe it has to do with the qt5webkit source not working with the
> g++ version you got. Your g++ might be too new. type_traits has changed 
> a bit over the past, so that *might* have something to do with it.

Yes, that's very likely my new toolchain version that is triggering this
issue. I had a build passing with a slightly older toolchain. The toolchain
update has been driven by the need of fresher kernel headers for other
packages, but a solution could be to use a custom toolchain with only the
kernel headers update, not updating g++.

>  > and qtwebkit does not look alive, based on latest commits dates).
> It was deprecated in Qt 5.5 back in 2015. Some people forked it and kept 
> it alive until 2019 or so, and now there is another fork going on here:
>
> https://github.com/movableink/webkit
>
> The "official" recommendation is to use QtWebEngine or QtWebView, 
> whatever is more appropriate. But I could not get either of them to 
> build with buildroot, so YMMV.
>
> An embedded version of webkit is WPE, which is also available in 
> buildroot as WPEWEBKIT: https://webkit.org/wpe/

Thanks for the confirmation and the hints for new packages. I have given a
quick try to the fork, but it does not look any better. Some branches
mentioned in the README can not even be found in the repo. I guess I'll
need to get rid of/replace those dependencies.

Thanks,

Alexis
>
> Best regards
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot




-- 
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-07-16 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 12:42 [Buildroot] Build failure on qt5webkit Alexis Lothoré via buildroot
2025-07-16  6:19 ` Philipp Ludwig
2025-07-16 16:21   ` Alexis Lothoré via buildroot [this message]
2025-12-28 19:38 ` Thomas Petazzoni via buildroot

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=DBDM80RGBKL3.28PXMVWQU0RW8@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=philipp.ludwig@passerro.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