On Thu, Jul 14, 2016 at 12:18:02AM +0200, Enrico Forestieri wrote: > This is because the code first checks for the existence of qtchooser > and then assumes that moc & company understand the -qt=qt5 option. > Given that you first set the correct PATH, the moc in > /usr/BUILD/BuildQt5-dev/qtbase/bin is actually executed, and it > doesn't understand that option. Essentially, this occurs because > the full path to the qt tools is not retained anymore. > I have a setup similar to yours and incurred in a similar problem > which I tried to correct at f0aa1299. The solution is using the > --with-qt-dir option, without setting PATH and PKG_CONFIG_PATH. > This should work: > > export MYQTDIR=/usr/BUILD/BuildQt5-dev/qtbase > ./autogen.sh && ./configure --enable-qt5 --with-qt-dir=$MYQTDIR && make
Nice that is cleaner. I might transition to it. I often use my build script for older commits though so if that only works as of f0aa1299, I will wait. > > The following command also does not work with this commit: > > > > ./autogen.sh && ./configure --enable-qt5 && make > > > > It gives the following error: > > > > configure: error: cannot compile a simple Qt executable. Check you have > > the right $QTDIR. > > Strange, this should work and use the Qt5 from the system. I was not clear. I don't have Qt 5 dev libs; I have Qt 4 deb libs. > However, I agree that setting PATH and PKG_CONFIG_PATH as you do > it has to work. Please try the attached patch. The patch works well for me. Thanks. Scott
signature.asc
Description: PGP signature
