On Monday 02 November 2015 16:50:33 Michal Marek wrote: > On Mon, Nov 02, 2015 at 08:46:55AM -0500, Thiago Macieira wrote: > > On Monday 02 November 2015 11:36:43 Michal Marek wrote: > > > On 2015-11-02 04:20, Thiago Macieira wrote: > > > > - qtver=`qmake -query QT_VERSION` || { \ > > > > + qtver=`qmake -query QT_VERSION` || \ > > > > + qtver=`qmake-qt5 -query QT_VERSION` || \ > > > > + qtver=`qmake-qt4 -query QT_VERSION` || { \ > > > > > > The qtlibdir= etc assignments below still use qmake directly, plus this > > > will print an error if the command is not called "qmake." As Alexey > > > says, we do not need qmake, we need moc and the cflags / ldflags. Since > > > pkg-config worked for us previously, I suggest to use pkg-config again > > > and just check which of QtGui or Qt5Widgets is available. > > > > Here's an attempt using pkg-config. > > Works for me on openSUSE, it just started to prefer Qt5 now. But it > correctly builds against Qt4 if Qt5 is not available.
That's a consequence of using pkg-config. Now you can no longer choose your preferred Qt version by setting QT_SELECT, like the qmake solution would have allowed, as recommended by the Qt Project. At least, the qtchooser shell function extension does set PKG_CONFIG_PATH, so if you install a different version elsewhere, that version should be picked up. It would have been the same with CMake too, btw. Alexey, did this solve the problem for you? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/