[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: Ben Abbott
Subject: [Octave-bug-tracker] [bug #55282] QT_CPPFLAGS and QT_LDFLAGS not always present when needed
Date: Sat, 29 Dec 2018 19:45:32 -0500 (EST)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0.2 Safari/605.1.15

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


My apologies, I haven't been as specific about the troubles on macOS as I
should be. With the upgrades to Qt 5.10 and 5.11, I didn't worry about the Qt
details. I was just happy to have Octave build, and didn't worry about the
"why".  With the present discussion (your input) the situation is clarifying
for me.

On macOS, pkg-config hasn't provided a root include path for any version of
Qt. For some versions the "-L/usr/.../lib" (5.11) needed to be added manually,
for other versions "-F/usr/.../lib" needed to be added (5.10, 5.12).

I expect all of this can be resolved if all frameworks and libraries were
present in a root lib directory (they are), and if all modules' include
directories were present in a root Qt include path. If that were done it would
resolve the Qt Creator problem as well as the autotools problem for building
with Qt (the autotools fix can piggy-back on the Qt Creator fix).


Reply to this item at:


  Message sent via Savannah

reply via email to

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