Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] sonic-visualiser: fix build
Date: Fri, 15 May 2020 18:59:33 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21989@inbox.vuxu.org> (raw)

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

There is a new pull request by newbluemoon against master on the void-packages repository

https://github.com/newbluemoon/void-packages sonic-visualiser
https://github.com/void-linux/void-packages/pull/21989

sonic-visualiser: fix build
- deprecated warnings were treated as errors
- remove unnecessary patch

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-sonic-visualiser-21989.patch --]
[-- Type: text/x-diff, Size: 1743 bytes --]

From c25a6ff6973985bbbc8495ffa9fe8fb0a80576fa Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Fri, 15 May 2020 18:50:53 +0200
Subject: [PATCH] sonic-visualiser: fix build

- deprecated warnings were treated as errors
- remove unnecessary patch
---
 .../patches/0001-Fix-header-file.patch               | 12 ------------
 srcpkgs/sonic-visualiser/template                    |  2 ++
 2 files changed, 2 insertions(+), 12 deletions(-)
 delete mode 100644 srcpkgs/sonic-visualiser/patches/0001-Fix-header-file.patch

diff --git a/srcpkgs/sonic-visualiser/patches/0001-Fix-header-file.patch b/srcpkgs/sonic-visualiser/patches/0001-Fix-header-file.patch
deleted file mode 100644
index cfc1d487529..00000000000
--- a/srcpkgs/sonic-visualiser/patches/0001-Fix-header-file.patch
+++ /dev/null
@@ -1,12 +0,0 @@
-diff --git a/svcore/base/RangeMapper.h b/svcore/base/RangeMapper.h
-index dd8ba94..4cdd924 100644
---- svcore/base/RangeMapper.h
-+++ svcore/base/RangeMapper.h
- #ifndef SV_RANGE_MAPPER_H
- #define SV_RANGE_MAPPER_H
- 
--#include <QString>
-+#include <qt5/QtCore/qstring.h>
- 
- #include "Debug.h"
- #include <map>
diff --git a/srcpkgs/sonic-visualiser/template b/srcpkgs/sonic-visualiser/template
index d0ac70c02fe..a80bd946a28 100644
--- a/srcpkgs/sonic-visualiser/template
+++ b/srcpkgs/sonic-visualiser/template
@@ -17,6 +17,8 @@ changelog="https://code.soundsoftware.ac.uk/projects/sonic-visualiser/repository
 distfiles="https://code.soundsoftware.ac.uk/attachments/download/2607/${pkgname}-${version}.tar.gz"
 checksum=e6e9dbec686c9dc94d32dff311eb0f6b44b63d3643285b3d8d908dfb9b22c790
 
+CXXFLAGS+=" -DQT_NO_DEPRECATED_WARNINGS"
+
 if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
 	makedepends+=" libatomic-devel"
 fi

             reply	other threads:[~2020-05-15 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 16:59 newbluemoon [this message]
2020-05-16  9:25 ` [PR PATCH] [Merged]: " Chocimier
  -- strict thread matches above, loose matches on Subject: below --
2019-11-12  5:26 [PR PATCH] sonic-visualiser: Fix build 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21989@inbox.vuxu.org \
    --to=newbluemoon@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).