Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: welle.io-2.0
Date: Mon, 11 Nov 2019 11:55:53 +0100	[thread overview]
Message-ID: <20191111105553.hkqJcVx1dnlIBDJzl-f0k_irfOnClrnk_tLC0w5dT3o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16318@inbox.vuxu.org>

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

There is an updated pull request by bra1nwave against master on the void-packages repository

https://github.com/bra1nwave/void-packages welle.io
https://github.com/void-linux/void-packages/pull/16318

New package: welle.io-2.0
If anyone reads this, please have a look at my other [package ](https://github.com/void-linux/void-packages/pull/14170) as well.

A patch file from https://github.com/void-linux/void-packages/pull/16318.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-welle.io-16318.patch --]
[-- Type: text/x-diff, Size: 1707 bytes --]

From 0d003dc89372bd09bc116ecae654306c68b196a0 Mon Sep 17 00:00:00 2001
From: bra1nwave <bra1nwave@protonmail.com>
Date: Sun, 10 Nov 2019 15:02:38 +0100
Subject: [PATCH] New package: welle-io-2.0

---
 srcpkgs/welle-io/template | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 srcpkgs/welle-io/template

diff --git a/srcpkgs/welle-io/template b/srcpkgs/welle-io/template
new file mode 100644
index 00000000000..a33095b3255
--- /dev/null
+++ b/srcpkgs/welle-io/template
@@ -0,0 +1,30 @@
+# Template file for 'welle-io'
+pkgname=welle-io
+version=2.0
+revision=1
+build_style=cmake
+wrksrc="welle.io-${version}"
+configure_args="$(vopt_bool airspy AIRSPY) $(vopt_bool rtlsdr RTLSDR)
+ $(vopt_bool soapysdr SOAPYSDR)"
+hostmakedepends="pkg-config"
+makedepends="$(vopt_if airspy libairspy-devel) $(vopt_if rtlsdr librtlsdr-devel)
+ $(vopt_if soapysdr SoapySDR-devel) qt5-devel qt5-declarative-devel
+ qt5-quickcontrols2-devel qt5-multimedia-devel qt5-charts-devel fftw-devel
+ lame-devel alsa-lib-devel faad2-devel mpg123-devel"
+short_desc="DAB/DAB+ Software Defined Radio (SDR)"
+maintainer="bra1nwave <bra1nwave@protonmail.com>"
+license="GPL-2.0-or-later"
+homepage="https://www.welle.io/"
+distfiles="https://github.com/AlbrechtL/welle.io/archive/v${version}.tar.gz"
+checksum=abfe999b6788ae57dfaaebea5e1db912565d60cc287c9eec4636b0e10eab4f9d
+
+build_options="airspy rtlsdr soapysdr"
+build_options_default="airspy rtlsdr soapysdr"
+
+desc_option_rtlsdr="Enable support for RTL-SDR"
+desc_option_airspy="Enable support for Airspy"
+desc_option_soapysdr="Enable support for SoapySDR"
+
+if [ "$CROSS_BUILD" ]; then
+	hostmakedepends+=" qt5-qmake qt5-host-tools"
+fi

  parent reply	other threads:[~2019-11-11 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 14:03 [PR PATCH] " voidlinux-github
2019-11-10 14:09 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-11 10:09 ` voidlinux-github
2019-11-11 10:55 ` voidlinux-github [this message]
2019-11-11 10:56 ` voidlinux-github
2019-11-11 10:59 ` [PR PATCH] [Updated] New package: welle-io-2.0 voidlinux-github
2019-11-12 14:25 ` [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=20191111105553.hkqJcVx1dnlIBDJzl-f0k_irfOnClrnk_tLC0w5dT3o@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).