Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New build-helper: qmake
Date: Mon, 04 Nov 2019 17:44:04 +0100	[thread overview]
Message-ID: <20191104164404.fOMvu-_FAw5ViKSyPjdN-eUPZWmKGO5lsBk5etNiaGU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16082@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

New build-helper: qmake
https://github.com/void-linux/void-packages/pull/16082

Description:
There are a couple of packages which have a mixed build-style, like when a configure script or a makefile calls `qmake`. This causes trouble in cross builds, because each style has its own setup, but in the current situation you can only have one: either a setup for, e.g., `gnu-configure` or `qmake` style.

This build-helper just creates qmake’s `qt.conf` (from the qmake build-style) and creates a wrapper-qmake to actually use this configuration. So that qmake can be set up correctly for cross builds when it is invoked by other styles.

Packages identified so far are: (local native and cross builds were all ok)

* abGate
* djview @leahneukirchen 
* gpsbabel @hanspolo 
  There is an update to 1.6.0, but in the current version Gmaps is patched out and the patch doesn’t apply anymore (might be a bit more to it now) so I didn’t update (don’t know about the implications).
* qjackctl @Piraty, I somewhat reverted your recent changes, are you OK with it? :)
* qsynth, also updated to 0.6.0.
* recoll, also updated to 1.26.1
  It now needs libxslt, but the `xslt-config` wrapper uses `xml2-config` which is hardcoded as `/usr/bin/xml2-config` so it’s not using the `xml2-config` wrapper and fails. As a quick workaround I patched it out in `pre_configure()`, but think this should be done when the wrapper is created.
* smplayer @Hoshpak 
* sonic-visualiser
* maybe some more ...

      parent reply	other threads:[~2019-11-04 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-03  7:45 [PR PATCH] " voidlinux-github
2019-11-03  9:32 ` voidlinux-github
2019-11-03 11:58 ` voidlinux-github
2019-11-03 14:01 ` voidlinux-github
2019-11-04 16:44 ` voidlinux-github [this message]

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=20191104164404.fOMvu-_FAw5ViKSyPjdN-eUPZWmKGO5lsBk5etNiaGU@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).