Package Details: qlcplus 4.13.0-2

Git Clone URL: (read-only, click to copy)
Package Base: qlcplus
Description: Q Light Controller Plus - The open DMX lighting desk software for controlling professional lighting fixtures.
Upstream URL:
Keywords: dmx lighting
Licenses: Apache
Conflicts: qlc, qlc-svn
Submitter: jlebleu
Maintainer: freaknils
Last Packager: freaknils
Votes: 30
Popularity: 0.59
First Submitted: 2013-04-13 15:54 (UTC)
Last Updated: 2024-03-20 12:28 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

mika.cousin commented on 2024-03-20 10:09 (UTC)

Hi! It seems that you need to install qt5-serialport first to compile this new version (4.13.0).

llelievr commented on 2021-03-05 15:27 (UTC)

@freaknils yep, the issue is mine actually ^^

freaknils commented on 2021-03-05 06:18 (UTC)

@kuerbiskakteen, @llelievr Seems to be an upstream problem

llelievr commented on 2021-03-04 22:37 (UTC)

@kuerbiskakteen Same issue. here

kuerbiskakteen commented on 2021-02-11 11:07 (UTC) (edited on 2021-02-11 13:47 (UTC) by kuerbiskakteen)

I have an error:

libftdi-interface.cpp: In static member function 'static QList<DMXInterface*> LibFTDIInterface::interfaces(QList<DMXInterface*>)': libftdi-interface.cpp:138:37: error: 'struct ftdi_context' has no member named 'usb_ctx' 138 | if (libusb_get_device_list(ftdi.usb_ctx, &devs) < 0) | ^~~~~~~ libftdi-interface.cpp:182:37: error: cannot convert 'libusb_device' to 'usb_device' 182 | ftdi_usb_get_strings(&ftdi, dev, vend, 256, nme, 256, ser, 256); | ^~~ | | | libusb_device In file included from libftdi-interface.h:24, from libftdi-interface.cpp:31: /usr/include/ftdi.h:376:76: note: initializing argument 2 of 'int ftdi_usb_get_strings(ftdi_context, usb_device, char, int, char, int, char, int)' 376 | int ftdi_usb_get_strings(struct ftdi_context ftdi, struct usb_device dev, | ~~~~~~~~~~~~~~~~~~~^~~ In file included from libftdi-interface.cpp:28: /usr/include/libusb-1.0/libusb.h:944:8: note: class type 'libusb_device' is incomplete 944 | struct libusb_device; | ^~~~~~~~~~~~~

Any workarounds?

freaknils commented on 2020-11-14 12:05 (UTC)

@yar, @nkaminski: Sorry for the late response. Updates done :-)

yar commented on 2020-11-13 23:40 (UTC)

@freaknils please add the qmake flag from rahix. It's necessary to build the package.

nkaminski commented on 2020-10-08 04:50 (UTC)

I can confirm that this builds on ARMv7 architecture as well. Would it be possible to update the arch variable to include 'armv7h' as well?

arch=('i686' 'x86_64' 'armv7h')

rahix commented on 2020-07-18 09:03 (UTC)

tmladek: You can work around the error by editing PKGBUILD and adjusting the qmake invocation like this:

qmake-qt5 QMAKE_CXXFLAGS=-Wno-deprecated-declarations

tmladek commented on 2020-07-10 08:38 (UTC)

Can confirm error about deprecated declarations:

chaserrunner.cpp: In static member function ‘static void ChaserRunner::shuffle(QVector<int>&)’: chaserrunner.cpp:383:34: error: ‘int qrand()’ is deprecated: use QRandomGenerator instead [-Werror=deprecated-declarations] 383 | qSwap(data[i], data[qrand() % (i + 1)]); | ^ In file included from /usr/include/qt/QtCore/qelapsedtimer.h:43, from /usr/include/qt/QtCore/QElapsedTimer:1, from chaserrunner.cpp:22: /usr/include/qt/QtCore/qglobal.h:1277:80: note: declared here 1277 | Q_CORE_EXPORT QT_DEPRECATED_VERSION_X_5_15("use QRandomGenerator instead") int qrand(); | ^~~~~ g++ -c -pipe -Werror -Wno-unused-local-typedefs -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -Wall -Wextra -D_REENTRANT -fPIC -DQT_NO_DEBUG_OUTPUT -DHAS_FFTW3 -DQT_NO_DEBUG -DQT_MULTIMEDIA_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_SCRIPT_LIB -DQT_CORE_LIB -I. -I../audio/src -I../../plugins/interfaces -I../../hotplugmonitor/src -isystem /usr/include/qt -isystem /usr/include/qt/QtMultimedia -isystem /usr/include/qt/QtGui -isystem /usr/include/qt/QtNetwork -isystem /usr/include/qt/QtScript -isystem /usr/include/qt/QtCore -I. -I/usr/lib/qt/mkspecs/linux-g++ -o cuestack.o cuestack.cpp cc1plus: all warnings being treated as errors

Any workarounds? Should the maintainer be notified?