maybe using ./configure --disable-qt4 (or its equivalent, --enable-qt5)... ?
EDIT: maybe you'll need also to tell which Qt install path is precisely what you want, using the additional --with-qt=QTDIR configure directive?
although it's perfectly possible to build and run qtractor on Qt5 just fine please note that it is not currently the recommended production target.
if you still wish to go that way be advised that you'll ditch all those LV2 plugin UI amenities as provided by libSUIL in the process--aning that the vast majority of LV2 plugins won't show their own GUI whatsoever unless they provide a proper lv2_external_ui extension and even though they do so, if they happen to be Qt4 based still (eg. vee one suite, qmidiarp), they will crash the whole show at 1st (non) sight. sad but true.
maybe using
./configure --disable-qt4(or its equivalent,--enable-qt5)... ?EDIT: maybe you'll need also to tell which Qt install path is precisely what you want, using the additional
--with-qt=QTDIR configure directive?although it's perfectly possible to build and run qtractor on Qt5 just fine please note that it is not currently the recommended production target.
if you still wish to go that way be advised that you'll ditch all those LV2 plugin UI amenities as provided by libSUIL in the process--aning that the vast majority of LV2 plugins won't show their own GUI whatsoever unless they provide a proper lv2_external_ui extension and even though they do so, if they happen to be Qt4 based still (eg. vee one suite, qmidiarp), they will crash the whole show at 1st (non) sight. sad but true.
byee