From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Ballasi <thomas.ballasi@savoirfairelinux.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Peter Seiderer <ps.report@gmx.net>,
Julien Corjon <corjon.j@ecagroup.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/qt5/qt5webkit: fix generated artifacts
Date: Fri, 11 Aug 2023 09:23:31 +0200 [thread overview]
Message-ID: <20230811092331.36236311@windsurf> (raw)
In-Reply-To: <20220929181350.1026033-1-thomas.ballasi@savoirfairelinux.com>
Hello Thomas,
As part of an effort to clear up our backlog, I stumbled across this
patch of yours, which has never been applied.
However, looking at the issue, I see that both qt-webkit-kiosk and
python-pyqt5 were indeed failing to build until November/December 2022,
being unable to find the "webkit" Qt module. But since then, we haven't
had any further build failure for those two packages:
http://autobuild.buildroot.net/?reason=qt-webkit-kiosk%
http://autobuild.buildroot.net/?reason=python-pyqt5%
I don't immediately see what has changed in qt5webkit that could have
fixed the issue.
Does this issue still exists in the current Buildroot master?
Thanks for your feedback,
Thomas
On Thu, 29 Sep 2022 14:13:50 -0400
Thomas Ballasi <thomas.ballasi@savoirfairelinux.com> wrote:
> Generated artifacts of the installation process were wrongly located,
> causing packages using qt5webkit (qt-webkit-kiosk and python-pyqt5) to
> fail at build time.
>
> Firstly, *.h files are wrongly located a directory below where supposed
> (inside qt5/ directory). This is caused by using DATADIR which assumed
> include files were to be located in sysroot/usr/include/. Disabling this
> variable by removing it from build options leads to a correct behavior.
>
> Secondly, in order to locate *.pri artifacts correctly, we set the conf
> option CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT on, which in turn
> sets the variable KDE_INSTALL_USE_QT_SYS_PATHS on, for the following
> reasons:
>
> 1. *.pri files are wrongly located in the host's and target's sysroot
> directores while buildroot implements its own mkspecs directory.
> By setting KDE_INSTALL_USE_QT_SYS_PATHS on, mkspecs modules are now
> being installed in host's data dir (ECM_MKSPECS_INSTALL_DIR is set
> accordingly @ line 102 in Source/cmake/ECMGeneratePriFile.cmake).
> This also required to prevent using the CMake package's default
> DATADIR variable, as done previously, as it enforced to install
> artifacts under the sysroot directory.
>
> 2. *.pri files' content have hardcoded include and library paths. This
> has been corrected by setting on KDE_INSTALL_USE_QT_SYS_PATHS as
> their content is written according to this value (see line 514 and
> 739 in file Source/WebKit/PlatformQt.cmake).
>
> Regression happened when qt5webkit started using cmake-package at commit
> df0b0fe6919c0d0f3750f439a3cfa765232bd569.
>
> Fixes:
> https://bugs.buildroot.org/show_bug.cgi?id=14606
>
> Signed-off-by: Thomas Ballasi <thomas.ballasi@savoirfairelinux.com>
> ---
> package/qt5/qt5webkit/qt5webkit.mk | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/package/qt5/qt5webkit/qt5webkit.mk b/package/qt5/qt5webkit/qt5webkit.mk
> index 6912359674..8310ef20c8 100644
> --- a/package/qt5/qt5webkit/qt5webkit.mk
> +++ b/package/qt5/qt5webkit/qt5webkit.mk
> @@ -51,10 +51,18 @@ QT5WEBKIT_CONF_OPTS += -DENABLE_SAMPLING_PROFILER=OFF
> endif
>
> QT5WEBKIT_CONF_OPTS += \
> + -DCMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT=ON \
> -DENABLE_TOOLS=OFF \
> -DPORT=Qt \
> -DPYTHON_EXECUTABLE=$(HOST_DIR)/bin/python3 \
> -DSHARED_CORE=ON \
> -DUSE_LIBHYPHEN=OFF
>
> +QT5WEBKIT_INSTALL_STAGING_OPTS = install/fast
> +
> +define QT5WEBKIT_INSTALL_TARGET_CMDS
> + $(TARGET_MAKE_ENV) $(BR2_CMAKE) --install $(QT5WEBKIT_BUILDDIR) \
> + --prefix $(TARGET_DIR)/usr
> +endef
> +
> $(eval $(cmake-package))
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-11 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 21:45 [Buildroot] [PATCH] package/qt5/qt5webkit: fix generated artifacts Thomas Ballasi
2022-09-29 10:43 ` Giulio Benetti
2022-09-29 18:04 ` Thomas Ballasi
2022-09-29 18:13 ` [Buildroot] [PATCH v2] " Thomas Ballasi
2022-09-29 22:02 ` Giulio Benetti
2023-08-11 7:23 ` Thomas Petazzoni via buildroot [this message]
2023-10-02 20:01 ` Yann E. MORIN
2025-12-28 19:52 ` 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=20230811092331.36236311@windsurf \
--to=buildroot@buildroot.org \
--cc=corjon.j@ecagroup.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=ps.report@gmx.net \
--cc=thomas.ballasi@savoirfairelinux.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox