All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14931] package/qt5/qt5webengine: build fails with unicode/uchar.h not found
Date: Wed, 25 Oct 2023 21:46:44 +0000	[thread overview]
Message-ID: <bug-14931-163-fCOPEuzNur@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14931-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=14931

--- Comment #5 from Kadir Yilmaz <kadir.c.yilmaz@gmail.com> ---
I have just submitted a patch to this  bug:

https://lists.buildroot.org/pipermail/buildroot/2023-October/677826.html

It manifests itself in 2 ways:

- If the build host has unicode/uchar.h in default include dirs, e.g. on 
ubuntu /usr/include/unicode/uchar.h provided by libicu-dev package, build finds
the header and later on linking fails.

- Otherwise fails with the error described in this bug.

By removing "webengine-icu" config option qt5webengine, build uses the one
bundled in qt, which addresses at least the build failure.

Here are the some hints in qt config files:

qtwebengine/src/core/configure.json:16:            "webengine-icu": { "type":
"enum", "name": "webengine-system-icu", "values": { "system": "yes", "qt": "no"
} },

qtwebengine/config_help.txt:8:  -webengine-icu ................. Use system ICU
libraries [system/qt]

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-10-25 21:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 16:40 [Buildroot] [Bug 14931] New: package/qt5/qt5webengine: build fails with unicode/uchar.h not found bugzilla
2022-08-23 15:13 ` [Buildroot] [Bug 14931] " bugzilla
2022-08-24  9:49 ` bugzilla
2023-05-09 13:50 ` bugzilla
2023-09-11 18:41 ` bugzilla
2023-10-25 21:46 ` bugzilla [this message]
2024-06-15 15:03 ` bugzilla

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=bug-14931-163-fCOPEuzNur@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.