From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jesse Van Gavere <jesseevg@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/qt6/qt6base: extend qt6 configuration
Date: Thu, 25 Aug 2022 10:43:42 +0200 [thread overview]
Message-ID: <20220825104342.61d691ac@windsurf> (raw)
In-Reply-To: <20220825073951.3920874-1-jesseevg@gmail.com>
Hello Jesse,
On Thu, 25 Aug 2022 09:39:51 +0200
Jesse Van Gavere <jesseevg@gmail.com> wrote:
> This will bring the qt6base functionality mostly on par with the qt5base
> package, building the package has been tested to the best of my ability
> and went without error as far as I can test.
> One bug to be noted is that for the GUI with fontconfig without harfbuzz
> support, this will produce incorrectly rendered text for version 6.3.1,
> see https://bugreports.qt.io/browse/QTBUG-101430
> I have however already verified that 6.3.2 and 6.4.0 will fix this issue
> so I've decided not to add harfbuzz as a fontconfig dependency as a
> version bump (which should be soon) will fix it.
Yes, let's bump to 6.4.0 then.
> Also add the version hashes for qt6base.
>
> Signed-off-by: Jesse Van Gavere <jesseevg@gmail.com>
Overall, this needs to be split into a number of patches:
- One adding the hash file, with just the hash of the tarball
- One adding the license information (which is totally missing today,
and I noticed due to your addition of the hash file) together with
the hashes of the license files
- Several patches adding the different options. I'm not too keen on
copy/pasting directly the qt5 logic, as I'm not sure all the
dependencies are exactly the same, so let's do this one feature at a
time.
> +ifeq ($(BR2_ENABLE_DEBUG),y)
> +QT6BASE_CONF_OPTS += -DCMAKE_BUILD_TYPE=Debug
> +else
> +QT6BASE_CONF_OPTS += -DCMAKE_BUILD_TYPE=Release
> +endif
This is already handled by the cmake-package infrastructure, do no need
to handle CMAKE_BUILD_TYPE.
> +ifeq ($(BR2_TOOLCHAIN_HAS_LIBATOMIC),y)
> +# Qt 5.8 needs atomics, which on various architectures are in -latomic
> +QT6BASE_CONF_OPTS += -DCMAKE_SHARED_LINKER_FLAGS="-latomic"
Is this also needed with Qt6 ? (Most likely yes, but the comment is
weird, another reason why I don't like the copy/pasting from Qt5).
Thomas
--
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:[~2022-08-25 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 7:39 [Buildroot] [PATCH 1/1] package/qt6/qt6base: extend qt6 configuration Jesse Van Gavere
2022-08-25 8:41 ` Yann E. MORIN
2022-08-25 8:43 ` Thomas Petazzoni via buildroot [this message]
2022-08-25 8:52 ` Jesse Van Gavere
2022-08-25 12:15 ` Giulio Benetti
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=20220825104342.61d691ac@windsurf \
--to=buildroot@buildroot.org \
--cc=jesseevg@gmail.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