Commit 3e71b623 authored by Sören Tempel's avatar Sören Tempel
Browse files

testing/libfm-qt: fix build with recent Qt

parent 6eecb5ff
......@@ -12,7 +12,8 @@ makedepends="
"
subpackages="$pkgname-dev"
options="!check" # No testsuite
source="https://github.com/lxqt/libfm-qt/releases/download/$pkgver/libfm-qt-$pkgver.tar.xz"
source="https://github.com/lxqt/libfm-qt/releases/download/$pkgver/libfm-qt-$pkgver.tar.xz
qt-5.15.3.patch"
build() {
if [ "$CBUILD" != "$CHOST" ]; then
......@@ -30,4 +31,7 @@ build() {
package() {
DESTDIR="$pkgdir" cmake --build build --target install
}
sha512sums="5de63408a641b0e77cb319952e428aee9cd35db9ec3e6726a8327ebc53f5641cf66b28dbabd96797c64a253b1e41421dbe05dcb9f4bc7941bd92676bbfa9cc84 libfm-qt-0.16.0.tar.xz"
sha512sums="
5de63408a641b0e77cb319952e428aee9cd35db9ec3e6726a8327ebc53f5641cf66b28dbabd96797c64a253b1e41421dbe05dcb9f4bc7941bd92676bbfa9cc84 libfm-qt-0.16.0.tar.xz
826d24cfc4cb1fd3c139a2644a6e4d30fb8c418e64cd9728ff2f2eb1f42370b4dedf488d6e173a41e57c20ca8c833044f3c2e7162d75e48c576d962b0bb6b15c qt-5.15.3.patch
"
From 868f0d36979c6930efcc8be20ed355cc1205723c Mon Sep 17 00:00:00 2001
From: Chiitoo <Chiitoo@users.noreply.github.com>
Date: Sat, 21 Nov 2020 03:52:22 +0200
Subject: [PATCH] Fix compiling with Qt >=5.15.3 (#588)
After a Qt upstream change [1], certain assignments that were not
caught by the compiler will now fail hard due to 'use of deleted
function'.
1. https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f8ad329f7ee
---
src/filedialog.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/filedialog.cpp b/src/filedialog.cpp
index 51754ce0..ef28696e 100644
--- a/src/filedialog.cpp
+++ b/src/filedialog.cpp
@@ -1109,7 +1109,7 @@ void FileDialog::setMimeTypeFilters(const QStringList& filters) {
nameFilter += suffix;
nameFilter += QLatin1Char(' ');
}
- nameFilter[nameFilter.length() - 1] = ')';
+ nameFilter[nameFilter.length() - 1] = QLatin1Char(')');
}
nameFilters << nameFilter;
}
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment