From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: build-style/qmake: add support for Qt6
Date: Thu, 02 Mar 2023 01:52:10 +0100 [thread overview]
Message-ID: <20230302005210.RBYWRFn0LKQHW_YURiNj6Zkm0_mGGwjOTJFRR1MV7rw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42354@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]
There's a merged pull request on the void-packages repository
build-style/qmake: add support for Qt6
https://github.com/void-linux/void-packages/pull/42354
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
There's no `qt6-doc` package (compared to `qt5-doc`) or `qt6-examples` subpackage (compared to `qt5-examples`) but those could just be ignored I suppose
~~There's a big problem: cross-compiling any Qt6 `qmake` package quickly results in something like `make: *** No rule to make target '/usr/libexec/moc', needed by '.moc/main.moc'. Stop.`~~
~~Native builds still work as expected however already. For a testing tree see [my `qt6-qmake-demo` tree](https://github.com/JamiKettunen/void-packages/commits/qt6-qmake-demo) and try e.g. `./xbps-src pkg qt6-qpa-hwcomposer-plugin` vs `./xbps-src pkg -a aarch64 qt6-qpa-hwcomposer-plugin` on a glibc masterdir.~~
~~As per https://forum.qt.io/topic/137300/qtpaths-return-incorrect-path `ln -s /usr/lib/qt6/libexec/moc /usr/libexec/moc` would probably work as a really ugly hack, but is there someone around (perhaps @Johnnynator?) who knows how this could be fixed properly, and maybe even upstream? Here's a few other places where the same error can be seen:~~
- ~~https://community.nxp.com/t5/i-MX-Processors/Imx8mp-cmake-creat-qt6-project-with-an-error-usr-libexec-moc-no/m-p/1567183~~
- ~~https://gobolinux.discourse.group/t/system-index-libexec-is-empty-issue/101~~
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2023-03-02 0:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 1:03 [PR PATCH] " JamiKettunen
2023-02-20 9:50 ` Johnnynator
2023-02-22 15:35 ` sgn
2023-02-22 16:05 ` sgn
2023-02-22 16:10 ` sgn
2023-03-01 13:09 ` [PR PATCH] [Updated] " JamiKettunen
2023-03-01 13:10 ` JamiKettunen
2023-03-01 13:15 ` sgn
2023-03-01 13:16 ` sgn
2023-03-01 14:34 ` [PR PATCH] [Updated] " JamiKettunen
2023-03-01 17:58 ` JamiKettunen
2023-03-02 0:52 ` sgn [this message]
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=20230302005210.RBYWRFn0LKQHW_YURiNj6Zkm0_mGGwjOTJFRR1MV7rw@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).