From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] qt5: update to 5.13.0
Date: Sun, 30 Jun 2019 12:06:46 +0200 [thread overview]
Message-ID: <20190630100646.EWK0_jfAg5Su-l4UlvhUiigj1cVSN6q6Qm8awWqSN9I@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: 1832 bytes --]
New comment by newbluemoon on void-packages repository
https://github.com/void-linux/void-packages/pull/11891#issuecomment-507023934
Comment:
I tried with the `fmit` package. The problem was that `qmake` hardcoded the required qt-libraries `fmit` is linked to in the `Makefile` when generating it with a full path (`/usr/lib/...`) which fails, of course, when cross-compiling.
The `qt.conf` has to be in `.../masterdir/usr/lib/qt5/bin/`. For now I just put it there manually. I used the one from above, just changed
Libraries=/usr/lib
to
Libraries=/usr/armv7l-linux-musleabihf/usr/lib
and that worked. `qmake` used the right paths in the generated `Makefile` and the package was built successfully. Just havenât tested it on my RPi, but donât think there will be a problem.
It would be nice to do the same for the includes so that the required qt-modules donât have to be added to `hostmakedepends` in the cross-case anymore, but the required `*.pri` files in `/usr/lib/qt5/mkspecs/modules/` are still missing in the cross-devel-packages. The same persisting problem I mentioned above. But we will find a solution one day! ;)
Perhaps itâs best to generate `qt.conf` in the build-style and insert the corresponding target architecture there. Then after the build remove the file.
A sidenote: You can check if `qmake` uses `qt.conf` when you `xbps-src chroot` into the masterdir and run `qmake -query`. The modified values should be displayed.
However, I also tested `zrandr` and there was a problem with `lrelease`. But this could be an entirely different problem. Iâll look into it.
Also, I think it might be a good idea to check all qmake-style packages if other problems arise or if changing that path leads to new ones. Anyway, Iâll try to check some more. :)
next prev parent reply other threads:[~2019-06-30 10:06 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
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 [this message]
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=20190630100646.EWK0_jfAg5Su-l4UlvhUiigj1cVSN6q6Qm8awWqSN9I@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).