Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: flysight-viewer-qt-git r540.131f465-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/flysight-viewer-qt-git.git (read-only, click to copy)
Package Base:	flysight-viewer-qt-git
Description:	Viewer application for flysight GPS log data
Upstream URL:	https://github.com/flysight/flysight-viewer-qt
Keywords:	flysight
Licenses:	unknown
Conflicts:	flysight-viewer-qt
Provides:	flysight-viewer-qt
Submitter:	mcoffin
Maintainer:	mcoffin
Last Packager:	mcoffin
Votes:	0
Popularity:	0.000000
First Submitted:	2017-08-21 20:09 (UTC)
Last Updated:	2017-08-29 18:49 (UTC)

Dependencies (5)

libvlc-qt^AUR (libvlc-qt-git^AUR)
qt5-base (qt5-base-git^AUR, qt5-base-headless^AUR)
qt5-webkit^AUR (qt5-webkit-git^AUR, qt5-webkit-movableink-git^AUR)
wwwidgets^AUR
git (git-git^AUR) (make)

Required by (0)

Sources (2)

Latest Comments

MarsSeed commented on 2023-10-30 13:17 (UTC)

Patching with current 0002-Fix-libvlc-qt-library-naming.patch fails.

intensity commented on 2022-08-17 04:09 (UTC) (edited on 2022-08-17 04:09 (UTC) by intensity)

Package is broken, here's how I was able to get it to build/run:

Drop the patch, they (you?) fixed this upstream
Add dependency qt5-webengine
Make new patch to use regular linker instead of lld (had issues for me at least)

Here's the patch I used for (3):

diff --git src/FlySightViewer.pro src/FlySightViewer.pro
index c7c9bd9..507f0b0 100644
--- src/FlySightViewer.pro
+++ src/FlySightViewer.pro
@@ -184,10 +184,6 @@ win32 {
     LIBS += -lVLCQtCore -lVLCQtQml -lVLCQtWidgets
 }

-unix {
-    CONFIG+=use_lld_linker
-}
-
 macx {
     QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.9
 }

Applied with this in prepare: $ patch -p1 -d src/ -i "$srcdir/regular_linker.patch" (I don't know how to properly make/apply patches...)

mcoffin commented on 2019-01-22 18:03 (UTC)

Upstream secret management issue with repository is causing build failures. Ultimately fixable yourself if you really need this to work now, but I'm going to hold off on updating the package until they've decided what they're going to do with it in the long run.