From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: "Peter Seiderer" <ps.report@gmx.net>,
"Julien Corjon" <corjon.j@ecagroup.com>,
"Gaël Portay" <gael.portay@collabora.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v8 4/5] package/qt5/qt5base: disable broken qmake sysrootify
Date: Wed, 27 Jul 2022 22:31:02 +0200 [thread overview]
Message-ID: <20220727223102.6daf1e27@windsurf> (raw)
In-Reply-To: <20220215015307.855341-4-james.hilliard1@gmail.com>
Hello James,
On Mon, 14 Feb 2022 18:53:06 -0700
James Hilliard <james.hilliard1@gmail.com> wrote:
> Currently the qmake gcc sysrootify path logic causes issues with
> per-package directories, disable automatic gcc sysroot for qt5base
> install and override all qt.conf paths manually to point to their
> correct locations.
Could you clarify which "issues" this is fixing? I am now looking at
this patch because it is the only one that has not been applied, 6
months after it has been posted, and the commit log is very fuzzy about
what the problem is, and how the commit fixes it.
I have just built the following defconfig successfully:
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_VFP=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_PER_PACKAGE_DIRECTORIES=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5MQTT=y
BR2_PACKAGE_QT5SCRIPT=y
BR2_PACKAGE_QT5SERIALBUS=y
# BR2_TARGET_ROOTFS_TAR is not set
Basically building with PPD, qt5base, and a limited set of qt5
packages. Could you describe the problem that you encountered, together
with a defconfig that allows to reproduce it?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-27 20:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 1:53 [Buildroot] [PATCH v8 1/5] package/qt5/qt5base: enable ccache via configure option James Hilliard
2022-02-15 1:53 ` [Buildroot] [PATCH v8 2/5] package/qt5/qt5webengine-chromium-catapult: new package James Hilliard
2022-05-17 19:53 ` Peter Korsgaard
2022-06-17 21:16 ` Peter Korsgaard
2022-02-15 1:53 ` [Buildroot] [PATCH v8 3/5] package/qt5/qt5webengine-chromium: " James Hilliard
2022-05-17 19:54 ` Peter Korsgaard
2022-06-17 21:16 ` Peter Korsgaard
2022-02-15 1:53 ` [Buildroot] [PATCH v8 4/5] package/qt5/qt5base: disable broken qmake sysrootify James Hilliard
2022-07-27 20:31 ` Thomas Petazzoni via buildroot [this message]
2022-08-02 22:44 ` James Hilliard
2022-08-21 20:18 ` Yann E. MORIN
2022-02-15 1:53 ` [Buildroot] [PATCH v8 5/5] package/qt5/qt5webengine: bump to version 5.15.8 James Hilliard
2022-05-17 7:35 ` Peter Korsgaard
2022-05-17 9:27 ` James Hilliard
2022-05-17 15:46 ` Peter Korsgaard
2022-05-17 19:40 ` James Hilliard
2022-05-17 19:53 ` Peter Korsgaard
2022-05-18 2:19 ` James Hilliard
2022-05-17 19:55 ` Peter Korsgaard
2022-05-16 21:02 ` [Buildroot] [PATCH v8 1/5] package/qt5/qt5base: enable ccache via configure option Peter Korsgaard
2022-05-16 21:29 ` 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=20220727223102.6daf1e27@windsurf \
--to=buildroot@buildroot.org \
--cc=corjon.j@ecagroup.com \
--cc=gael.portay@collabora.com \
--cc=james.hilliard1@gmail.com \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
/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.