[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease

[Dan Sebald]

Follow-up Comment #10, bug #48881 (project octave):

Your list looks similar to mine.  Hmm, I wonder if there is some way to get a
new local entry into that list?  Anyway, here's a link that indicates which
conf file to change:

http://askubuntu.com/questions/435564/qt5-installation-and-path-configuration

Here's what I'm seeing on my system:


sebald@ ~ $ ls /usr/lib/x86_64-linux-gnu/qtchooser/ -l
total 0
lrwxrwxrwx 1 root root 50 Apr 30 21:45 4.conf ->
../../../share/qtchooser/qt4-x86_64-linux-gnu.conf
lrwxrwxrwx 1 root root 50 Apr 30 21:45 5.conf ->
../../../share/qtchooser/qt5-x86_64-linux-gnu.conf
lrwxrwxrwx 1 root root 50 May 27  2015 default.conf ->
../../../share/qtchooser/qt4-x86_64-linux-gnu.conf
lrwxrwxrwx 1 root root 50 Apr 30 21:45 qt4.conf ->
../../../share/qtchooser/qt4-x86_64-linux-gnu.conf
lrwxrwxrwx 1 root root 50 Apr 30 21:45 qt5.conf ->
../../../share/qtchooser/qt5-x86_64-linux-gnu.conf

sebald@ ~ $ cat /usr/lib/x86_64-linux-gnu/qtchooser/default.conf 
/usr/lib/x86_64-linux-gnu/qt4/bin
/usr/lib/x86_64-linux-gnu


Oh hey, I wonder...  yes, I see.  I just placed a new file in that directory
and that shows up in the list, and I did the same in the ~/.config/qtchooser
directory:


sebald@ ~ $ ls /usr/lib/x86_64-linux-gnu/qtchooser
4.conf  5.conf  default.conf  qt4.conf  qt5.conf  qt5mybuild.conf

sebald@ ~ $ ls .config/qtchooser/
qt5nonsystem.conf

sebald@ ~ $ qtchooser -l
4
5
default
qt4-i386-linux-gnu
qt4-x86_64-linux-gnu
qt4
qt5-x86_64-linux-gnu
qt5
qt5mybuild
qt5nonsystem

sebald@ ~ $ qtchooser -run-tool=uic -qt=qt5nonsystem -v 
uic 5.2.1


This all seems to work fine.

T.M., when you use the following command

moc -qt5

you are bypassing qtchooser.  Whatever you set ~/.config/qtchooser/qt5.conf to
has no bearing on the above command.  After setting
~/.config/qtchooser/qt5.conf, you need to run

qtchooser -run-tool=moc -qt=qt5 -v

Or, you can call the conf file something other than qt5.conf, as I've
illustrated above.

The question for Octave make is, Should there be a pathway for the builder to
specify at qtchooser version other than 4/5 so that local Qt builds can be
used as I've illustrated above?  Or, should it fall back to the
"PKG_CONFIG_PATH=/somepath/pkgconfig ./configure" approach?


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48881>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/