[Top][All Lists]

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

[Octave-bug-tracker] [bug #55282] QT_CPPFLAGS and QT_LDFLAGS not always

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55282] QT_CPPFLAGS and QT_LDFLAGS not always present when needed
Date: Wed, 26 Dec 2018 15:43:56 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Follow-up Comment #4, bug #55282 (project octave):

I think that got cut off.

1. I think you might be confusing a couple points about QT_CPPFLAGS. One thing
is that trying to override QT_CPPFLAGS and QT_LDFLAGS from the shell
environment when calling configure doesn't do anything. If I run

./configure --whatever ... QT_CPPFLAGS=-I/tmp

that override has no effect. Same with exporting it in the shell. The only way
at the moment (I think) to have QT_CPPFLAGS set correctly is to have a
correctly configure pkg-config for Qt.

2. Is pkg-config for Qt on your system correct or not? You have shown that it
returns /usr/local/Cellar/qt/5.12.0/lib/QtGui.framework/Headers and
/usr/local/Cellar/qt/5.12.0/lib/QtCore.framework/Headers. Are those
directories correct and complete? Does qvariant.h exist under
/usr/local/Cellar/qt/5.12.0/lib/QtCore.framework/Headers/QtCore (I think that
was one of the missing header files in one of your other threads).

3. If I had a GNU/Linux system with Qt installed in a non-standard location
and no pkg-config working for it, I would use CPPFLAGS to point to the
directories needed. This is a feature, not a bug.

But, assuming you do have pkg-config set correctly and those -I options are
correct, the header files do exist, then you shouldn't need to set CPPFLAGS at


Reply to this item at:


  Message sent via Savannah

reply via email to

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