From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] qt5: update to 5.13.0
Date: Sat, 29 Jun 2019 04:44:42 +0200 [thread overview]
Message-ID: <20190629024442.nOJUiFwpdFfhwT4CuppcpVVOf_8plJbv0CDEJZiKiXg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11891@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/11891#issuecomment-506920374
Comment:
@pullmoll Do you have an idea how we could fix our qmake build-style/qmake for cross compiling that wouldn't be a tremendous amount of work?
Longer version:
A qmake binary only ever supports one target and has things like `QT_SYSROOT` and `QT_INSTALL_LIBS` hardcoded in the resulting binary so they can't be overwritten at runtime by a config file or flag. There are only 4 options to solve this for Void visivle for me:
- Build qtbase two times for every cross target, once as cross packages as currently and a 2nd with the same config for the host and only grab qmake out of there (wastes a ton of ressources on the builder)
- Add a way for xbps-src to spill out a cross target package and a build arch package (probably quite complex, and would (at least currently) only be needed for qt)
- manually mess with the provided Makefile (probably the easiest way)
```make EXTRA_CXXFLAGS="-I/usr/include/qt5/QtCore/5.13.0/QtCore -I/usr/include/qt5/QtCore/5.13.0 -I/usr/include/qt5/QtCore -I/usr/include/qt5/ -DQMAKE_OPENSOURCE_VERSION" QT_MAJOR_VERSION=5 QT_MINOR_VERSION=13 QT_PATCH_VERSION=0 QT_VERSION=5.13.0 SOURCE_PATH=.. QMAKESPEC=/usr/lib/qt5/mkspecs/linux-aarch64-gnu-g++ BUILD_PATH=. RM_F="rm -rf" EXTRA_LFLAGS="-lQt5Bootstrap" -f Makefile.unix``` gives an unconfigured qmake
- Make the 107 packages that use the qmake build-style nocross
next prev parent reply other threads:[~2019-06-29 2:44 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11891@inbox.vuxu.org>
2019-06-13 12:34 ` [PR PATCH] [Updated] [WIP] qt5: update to 5.13beta3 voidlinux-github
2019-06-19 9:26 ` voidlinux-github
2019-06-19 9:26 ` voidlinux-github
2019-06-19 13:20 ` [PR PATCH] [Updated] [WIP] qt5: update to 5.13.0 voidlinux-github
2019-06-19 13:20 ` voidlinux-github
2019-06-19 15:12 ` voidlinux-github
2019-06-19 15:12 ` voidlinux-github
2019-06-19 15:15 ` voidlinux-github
2019-06-19 15:15 ` voidlinux-github
2019-06-19 16:13 ` voidlinux-github
2019-06-19 16:54 ` voidlinux-github
2019-06-19 22:30 ` voidlinux-github
2019-06-21 16:18 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-21 16:18 ` voidlinux-github
2019-06-21 16:22 ` voidlinux-github
2019-06-21 16:22 ` voidlinux-github
2019-06-24 23:10 ` voidlinux-github
2019-06-24 23:10 ` voidlinux-github
2019-06-29 2:44 ` voidlinux-github
2019-06-29 2:44 ` voidlinux-github [this message]
2019-06-29 2:45 ` voidlinux-github
2019-06-29 2:45 ` voidlinux-github
2019-06-29 5:35 ` voidlinux-github
2019-06-29 5:36 ` voidlinux-github
2019-06-29 5:45 ` voidlinux-github
2019-06-29 6:08 ` voidlinux-github
2019-06-29 19:46 ` voidlinux-github
2019-06-30 10:06 ` voidlinux-github
2019-07-01 22:48 ` voidlinux-github
2019-07-01 22:54 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-01 22:54 ` voidlinux-github
2019-07-02 0:53 ` voidlinux-github
2019-07-02 5:52 ` voidlinux-github
2019-07-06 20:01 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-06 20:01 ` voidlinux-github
2019-07-06 20:19 ` voidlinux-github
2019-07-06 20:19 ` voidlinux-github
2019-07-06 20:24 ` voidlinux-github
2019-07-06 20:24 ` voidlinux-github
2019-07-06 20:26 ` voidlinux-github
2019-07-10 1:22 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-10 1:22 ` voidlinux-github
2019-07-10 9:54 ` voidlinux-github
2019-07-10 22:31 ` voidlinux-github
2019-07-10 22:32 ` voidlinux-github
2019-07-11 4:15 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-11 4:15 ` voidlinux-github
2019-07-11 4:29 ` [PR PATCH] [Merged]: " voidlinux-github
2019-07-11 4:30 ` voidlinux-github
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=20190629024442.nOJUiFwpdFfhwT4CuppcpVVOf_8plJbv0CDEJZiKiXg@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).