From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] qt5 update to 5.14.0
Date: Fri, 20 Mar 2020 14:31:06 +0100 [thread overview]
Message-ID: <20200320133106.RFm2moIqAGnMnpu5yrCWx4i7Fa0mbrogFG__RPdMDNQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15310@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/15310#issuecomment-601701048
Comment:
> Just FYI I also have a branch where I've been trying to get 5.14.1 built:
> https://github.com/pullmoll/void-packages/tree/qt5-5.14
> This branch builds qt5 for native architectures. Cross building is where there's a lot of work left to do and for which I don't currently find sufficient time.
Non cross also works here :), cross compiling itself also works. Just qmake build styles are broken.
> well, I'm starting to think that we should move on and continue if something is not cross buildable.
I agree on that one for less used software, but Qt is quite popular and I'd argue that people with e.g. a Pinebook would like to have Qt applications in the repo. We should just get a native aarch64 builder...
next prev parent reply other threads:[~2020-03-20 13:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 23:27 [PR PATCH] [WIP] qt5 uptade " voidlinux-github
2019-10-15 11:21 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-15 11:21 ` voidlinux-github
2019-11-11 19:23 ` [PR PATCH] [Updated] [WIP] qt5 update " voidlinux-github
2019-11-12 0:23 ` voidlinux-github
2020-01-03 10:46 ` voidlinux-github
2020-01-28 17:04 ` voidlinux-github
2020-02-02 16:03 ` voidlinux-github
2020-03-18 18:37 ` streaksu
2020-03-18 18:45 ` Johnnynator
2020-03-18 21:27 ` travankor
2020-03-18 22:31 ` Johnnynator
2020-03-19 22:48 ` mintsuki
2020-03-19 23:52 ` q66
2020-03-19 23:54 ` Johnnynator
2020-03-20 6:25 ` travankor
2020-03-20 13:00 ` pullmoll
2020-03-20 13:17 ` xtraeme
2020-03-20 13:19 ` xtraeme
2020-03-20 13:29 ` Johnnynator
2020-03-20 13:31 ` Johnnynator [this message]
2020-03-20 15:03 ` pullmoll
2020-03-20 15:53 ` q66
2020-03-20 17:48 ` Chocimier
2020-03-22 23:43 ` mintsuki
2020-03-23 0:11 ` travankor
2020-03-23 0:57 ` q66
2020-03-23 7:55 ` travankor
2020-03-23 7:55 ` travankor
2020-03-23 7:58 ` travankor
2020-03-23 8:57 ` Johnnynator
2020-03-23 8:57 ` Johnnynator
2020-03-23 13:35 ` q66
2020-04-03 15:00 ` [PR PATCH] [Updated] " Johnnynator
2020-04-03 16:19 ` [PR PATCH] [Merged]: " Johnnynator
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=20200320133106.RFm2moIqAGnMnpu5yrCWx4i7Fa0mbrogFG__RPdMDNQ@z \
--to=johnnynator@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).