octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #48881] Build failure due to -qt5 flag for uic, rcc, moc, and lrelease
Date: Thu, 1 Sep 2016 02:14:13 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0

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

>From the description in "man qtchooser", it sounds as though that's what
qtchooser is intended for.  It doesn't seem so complicated relative to the
many other configurations within the project.

To make the locally built Qt compatible with qtchooser only requires defining
a file ~/.config/qtchooser/qt5.conf

/home/sebald/qt5build/qt5/bin
/home/sebald/qt5build

If there is no qtchooser installed, what to do?  Don't know, but certainly
something has to point Octave configuration to the utilities within the above
local directories.  The way I've done that is with something like:

PKG_CONFIG_PATH=/home/sebald/qt5build/qt5 ./configure

for any project that uses the autotools suite.  I do see on my system some
pkgconfig files for Qt5:


sebald@ /usr/lib/x86_64-linux-gnu/pkgconfig $ ls Qt*
Qt3Support.pc           Qt5Svg.pc                QtNetwork.pc
Qt5Bootstrap.pc         Qt5Test.pc               QtOpenGL.pc
Qt5Concurrent.pc        Qt5Widgets.pc            QtScript.pc
Qt5Core.pc              Qt5Xml.pc                QtScriptTools.pc
Qt5DBus.pc              QtCLucene.pc             QtSql.pc
Qt5Gui.pc               QtCore.pc                QtSvg.pc
Qt5Network.pc           QtDBus.pc                QtTest.pc
Qt5OpenGLExtensions.pc  QtDeclarative.pc         QtUiTools.pc
Qt5OpenGL.pc            QtDesignerComponents.pc  QtXmlPatterns.pc
Qt5PlatformSupport.pc   QtDesigner.pc            QtXml.pc
Qt5PrintSupport.pc      QtGui.pc
Qt5Sql.pc               QtHelp.pc


If there are some pkgconfig files appearing in the local Qt build, then
perhaps no alteration is needed for Octave config if the PKG_CONFIG_PATH
variable is pre-defined.  This is the approach I needed to use when debugging
OpenGL.  I had to first build a bunch of up-to-date libraries that OpenGL
uses, and I placed them all in /home/sebald/lib and the *.pc files went to
/home/sebald/lib/pkgconfig.  I had to keep pre-defining PKG_CONFIG_PATH to
that same directory for about five libraries, then for the OpenGL build, then
for Octave.  After doing all that, I could then edit the OpenGL nuveau (or
whatever) driver and change the driver behavior.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]