Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/3] package/qt5webengine: needs libxkbcommon
Date: Fri, 18 Sep 2020 22:01:59 +0200	[thread overview]
Message-ID: <20200918220159.3649dbdc@gmx.net> (raw)
In-Reply-To: <20200917230546.1beaf61f@windsurf.hq.k.grp>

Hello Thomas,

On Thu, 17 Sep 2020 23:05:46 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> On Tue, 15 Sep 2020 20:00:03 +0200
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > Fixes:
> >   subprocess.CalledProcessError: Command '['/home/seiderer/Work/Buildroot/build_rpi4_qt5_update_001/build/qt5webengine-5.15.1/src/core/pkg-config_wrapper.sh', '--variable=prefix', 'xkbcommon']' returned non-zero exit status 1
> >
> >   See //ui/events/keycodes/BUILD.gn:12:3: whence it was called.
> >     pkg_config("xkbcommon") {
> >     ^------------------------
> >   See //ui/events/ozone/layout/BUILD.gn:42:15: which caused the file to be included.
> >       deps += [ "//ui/events/keycodes:xkb" ]
> >                 ^-------------------------
> >   Project ERROR: GN run error!
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > Notes:
> >  - send as extra patch as I am not sure if the failure is caused by
> >    the version bump and/or by a combination from my buildroot config
>
> Unfortunately, I think we really need to understand if this is a change
> needed in relation to the bump or not, so that we know if it needs to
> go in a stable branch.
>
> At least in a simple build of qt5webengine in v5.15.0 I have not
> encountered this particular build failure. But perhaps it occurs only
> when you have a bunch of other dependencies enabled.
>
> The BUILD.gn file contains:
>
> if (use_xkbcommon) {
>   pkg_config("xkbcommon") {
>     packages = [ "xkbcommon" ]
>   }
> }
>
> And src/buildtools/config/linux.pri seems to be defining the value of
> use_xkbcommon:
>
>     qtConfig(build-qtwebengine-core):qtConfig(webengine-system-xkbcommon) {
>         gn_args += use_xkbcommon=true
>     } else {
>         gn_args += use_xkbcommon=false
>     }
>
> I've never been familiar enough with the .pri syntax though to
> understand what this is doing.
>
> Could you try to see if the problem really comes from the 5.15.1 bump ?

qt5webengine-5.15.0 with the same buildroot config
compiles fine without libxkbcommon, will try qt5webengine-5.15.1
with a striped down buildroot config to evaluate if some of
my buildroot config options enable the need for libxkbcommon...

Regards,
Peter

>
> Thanks!
>
> Thomas

  reply	other threads:[~2020-09-18 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 18:00 [Buildroot] [PATCH v1 1/3] package/qt5: bump version to 5.15.1 Peter Seiderer
2020-09-15 18:00 ` [Buildroot] [PATCH v1 2/3] package/qt5webengine: needs libxkbcommon Peter Seiderer
2020-09-17 21:05   ` Thomas Petazzoni
2020-09-18 20:01     ` Peter Seiderer [this message]
2020-09-15 18:00 ` [Buildroot] [PATCH v1 3/3] package/qt5webkit: fix bison-3.7.1 related compile failure Peter Seiderer
2020-09-17 21:06   ` Thomas Petazzoni
2020-09-18 20:03     ` Peter Seiderer
2020-09-17 20:57 ` [Buildroot] [PATCH v1 1/3] package/qt5: bump version to 5.15.1 Thomas Petazzoni
2020-09-18 20:05   ` Peter Seiderer

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=20200918220159.3649dbdc@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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