Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: sonic-visualiser: update to 4.0
Date: Sun, 27 Oct 2019 08:44:43 +0100	[thread overview]
Message-ID: <20191027074443.Q1WEoF2suGnJibRitBvgcovfbTsOu4O4bWDMzYdB5_s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15804@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

New comment by newbluemoon on void-packages repository

https://github.com/void-linux/void-packages/pull/15804#issuecomment-546669667

Comment:
The problem with sonic-visualiser is that it is a mixed build-style: gnu-configure runs qmake in the end so that in cross cases qmake isn’t set up properly. To work-around this I just copied the creation of the `qt.conf` file from the qmake build-style and made qmake use it.

The xlint error is because of creating the custom `qt.conf`. Everything else is fine now. Tested on x86_64, x86_64-musl, and armv7l-musl (RPi).

But I think there are some other templates which are mixed qmake build-styles. Would it make sense to create a qmake-cross-wrapper (but only when the build-style is not qmake) which sets up and uses a `qt.conf` file?

  parent reply	other threads:[~2019-10-27  7:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26  6:14 [PR PATCH] " voidlinux-github
2019-10-26  8:31 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-26  8:31 ` voidlinux-github
2019-10-26  8:45 ` voidlinux-github
2019-10-26  8:49 ` voidlinux-github
2019-10-27  6:03 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-27  6:03 ` voidlinux-github
2019-10-27  7:06 ` voidlinux-github
2019-10-27  7:06 ` voidlinux-github
2019-10-27  7:44 ` voidlinux-github [this message]
2019-10-29 15:09 ` voidlinux-github
2019-10-29 20:16 ` [PR PATCH] [Merged]: " 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=20191027074443.Q1WEoF2suGnJibRitBvgcovfbTsOu4O4bWDMzYdB5_s@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).