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

[Dan Sebald]

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

>From https://savannah.gnu.org/bugs/?48881#comment1

"
This does not work in the case that you have, where qtchooser is installed and
configured to work with the Qt versions installed from the Ubuntu
repositories, but you have also installed a local version of Qt and set PATH
appropriately.

One workaround would be to figure out how to configure the qtchooser program
to use your locally installed copy of Qt. 
"

The qtchooser doc suggests that locally installed versions should be
included:

http://manpages.ubuntu.com/manpages/wily/man1/qtchooser.1.html

"The  Qt  Chooser  provides  a  wrapper to switch between versions of Qt
development binaries when multiple versions like 4 and 5 are installed or
local Qt builds are to be used."

Of course, it doesn't say exactly how to do that.

Also, depending upon what tools are used to build Qt, there is often a package
directory that can be set prior to make, e.g., 

PKG_CONFIG_PATH=/home/sebald/local/lib/pkgconfig ./configure --prefix ~/local
--with-llvm-prefix=/home/sebald/local --disable-llvm-shared-libs

in which case all of the info about where the tools/libraries, etc. are
contained is in the pkgconfig directory.  When I built OSMesa on my old
system, I had to do this with about four or five software projects to get the
latest of everything.  Does T.M. simply need to add the proper PKG_CONFIG_PATH
for the local Qt prior to the Octave ./configure?

Anyway, I'd still be interested in seeing what T.M. sees for

qtchooser -l
qtchooser -run-tool=uic -qt=5 -v
qtchooser -run-tool=uic -qt=4 -v

and how it is that qtchooser should be able to work with locally installed Qt.

    _______________________________________________________

Reply to this item at:

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

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