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 08:08:20 +0200 [thread overview]
Message-ID: <20190629060820.HJxA9TODxOsHqOohKPfSpb94k3XgtDmxW02Ru2S74Is@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: 976 bytes --]
New comment by newbluemoon on void-packages repository
https://github.com/void-linux/void-packages/pull/11891#issuecomment-506930877
Comment:
@pullmoll this would surely be an explanation. ;)
Maybe you remember this issue: I tried to compile some qt5 program natively on my RPi and ran into an issue where the modules in `/usr/lib/qt5/mkspecs/modules/*.pri` werenât found. With the `qt.conf` from above (and some other minor adjustments) I was able to compile it; i.e. the right paths were used. However, I believe in the end the problem was that when the application used other qt5 modules besides the core it didnât work because the required `*.pri` files werenât available in the cross built devel package of the corresponding module. So there was an underlying problem we never got around to solve.
One more thing: the only way I was able to make `qmake` use the `qt.conf` was when both executable and configfile were residing in the same directory.
next prev parent reply other threads:[~2019-06-29 6:08 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 [this message]
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=20190629060820.HJxA9TODxOsHqOohKPfSpb94k3XgtDmxW02Ru2S74Is@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).