I needed to install a couple of packages which aren't in the README: libudev-dev and libfftw3-dev.
It then failed to link many of the test executables because they wanted -lfftw3. I tried putting this as a LIBS += in test.pro but it didn't want to inherit it.
I then tried QT Creator because I think you said that's what you use to develop with, Massimo. This seemed to make it build - goodness knows how - but the resulting executable needed LD_LIBRARY_PATH setting because it couldn't find the engine and ui libraries. I realise on my 12.04 machine it must have been using the installed ones all along - I was only looking at plugins.
Also, I think it always looks in /usr/lib/qt4/plugins for its plugins, which is a pain because they are all in separate directories before installation so you can't just symlink to it. Easiest thing was to install - can QT Creator do this?
(I've still got the ola plugin commented out in plugins.pro as I couldn't solve its dependency problems on 12.04.)
Any tips to sort out this awkward build process would be appreciated, thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I compile every day on Ubuntu 13.04 (from a terminal, not Qt Creator) and no problems at all.
When you install libfftw3-dev it drags in also the FFTW library but if you started to compile QLC+ before, it is possible that you need to make distclean and qmake/make again.
As for OLA, I usually compile it from sources. Never used their deb files.
Last edit: Massimo Callegari 2013-07-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I needed to install a couple of packages which aren't in the README: libudev-dev and libfftw3-dev.
It then failed to link many of the test executables because they wanted -lfftw3. I tried putting this as a LIBS += in test.pro but it didn't want to inherit it.
I then tried QT Creator because I think you said that's what you use to develop with, Massimo. This seemed to make it build - goodness knows how - but the resulting executable needed LD_LIBRARY_PATH setting because it couldn't find the engine and ui libraries. I realise on my 12.04 machine it must have been using the installed ones all along - I was only looking at plugins.
Also, I think it always looks in /usr/lib/qt4/plugins for its plugins, which is a pain because they are all in separate directories before installation so you can't just symlink to it. Easiest thing was to install - can QT Creator do this?
(I've still got the ola plugin commented out in plugins.pro as I couldn't solve its dependency problems on 12.04.)
Any tips to sort out this awkward build process would be appreciated, thanks!
The README file is not updated. Sorry.
I gave the fact that users follow the "QLC+ Build HOWTO" link from the QLC+ webiste and reach this Wiki page:
https://github.com/mcallegari/qlcplus/wiki/Linux-Build-HOWTO
I compile every day on Ubuntu 13.04 (from a terminal, not Qt Creator) and no problems at all.
When you install libfftw3-dev it drags in also the FFTW library but if you started to compile QLC+ before, it is possible that you need to make distclean and qmake/make again.
As for OLA, I usually compile it from sources. Never used their deb files.
Last edit: Massimo Callegari 2013-07-14